sprint-planner
Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.
pinned to #7f8ee3cupdated 2 weeks ago
Ask your AI client: “install skills/sprint-planner”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/sprint-plannermetahub onboarded this repo on the author's behalf.
If you own github.com/oxbshw/LLM-Agents-Ecosystem-Handbook on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
533
Last commit
2 weeks ago
Latest release
published
- #ai
- #ai-agent
- #ai-agents
- #fine-tuning
- #finetuning-llms
- #freamework
- #llm
- #llmops
- #local-development
- #mcp-server
- #memory
- #rag
- #rag-chatbot
- #voice-agent
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.7f8ee3c· 2 weeks ago
Documentation
41Description quality
20 words · 118 chars — "Use when planning the next sprint — turns ticket intake + team capacity into a p…"
README is present and substantial
19,199 chars · 20 sections · 2 code blocks
Tags / topics declared
14 total — ai, ai-agent, ai-agents, fine-tuning, finetuning-llms, freamework (+8)
README has usage / example sectionswarn
README has no Usage / Example / Quick start / Installation heading at any level
Add a `# Usage`, `## Quick start`, or similar section so end users can copy/paste a working invocation. Code blocks alone work too if there are several.
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrent7f8ee3cwarn2 weeks ago
Contents
When to use
- Start of a sprint cycle
- After a re-prioritization mid-cycle
- When intake outpaces capacity and you need a defendable plan
When NOT to use
- Daily standup (different cadence)
- Annual planning (different scope; use
roadmap-synthesizer)
Inputs
| Name | Type | Required | Notes |
|---|---|---|---|
tickets | list / path | yes | candidate work items with priority + estimates |
capacity | object | yes | per-engineer days available |
previous_carry | list | no | items rolling over from last sprint |
commitments | list | no | OKR / stakeholder commitments that must land |
Outputs
sprint-plan.md with: Sprint goal, Committed, Stretch, Non-goals, Risks.
Workflow
- Compute total capacity (days × team)
- Sort candidates: committed → carry → stretch
- Pack to ~85% of capacity (leave room for support / interrupts)
- Identify dependencies between items; surface blockers
- Surface explicit non-goals — what we are not doing this sprint and why
- Risks: anything that would cause spillover
References
Success criteria
- Committed work ≤ 85% of capacity
- Every committed item has an owner and an estimate
- Non-goals section is non-empty
- Risks include at least one "what could derail us"
Failure modes
- Capacity unknown → ask, don't guess
- Tickets without estimates → flag and exclude from "committed"
Reviews
No reviews yet. Be the first.
Related
Browser Use
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
Gpt Researcher
An autonomous agent that conducts deep research on any data using any LLM providers
Guizang Ppt Skill
AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts, social covers, and a WebGL/low-power presentation runtime.
mh install skills/sprint-planner