sprint-planner
Skill152 starsChanged 8 months agoMITView on GitHub
Sprint Goal (1 sentence) Recommended Backlog | Item | Estimate | Priority | Dependencies | Owner | Capacity Check - Capacity: [X points/days] - Planned: [total] - Buffer (20%): [amount] - Verdict: Over/Under/Right-sized Stretch Goals (if team finishes early) Risks to This Sprint Bad sprint plan (no capacity math, no priorities): Good sprint plan:
5 other projects use a version of this.
Adopted by
Most recently taken up by
- sunholo-data/ailangtheir own version, first seen Nov 6, 2026
- roborracle/agent-workflow-kittheir own version, first seen Aug 11, 2026
- patonkikh/APEStheir own version, first seen Jul 3, 2026
- hamzafarooq/claude-code-startertheir own version, first seen May 8, 2026
- SkyWalker2506/ccplugin-sprint-plannertheir own version, first seen Apr 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- hamzafarooq/claude-code-starter★ 145same name
- sunholo-data/ailang★ 38same name
- patonkikh/APES★ 3same name
- roborracle/agent-workflow-kit★ 0same name
- SkyWalker2506/ccplugin-sprint-planner★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- competitive-analysisSkill
- launch-checklistSkill
- metrics-definerSkill
- prd-writerSkill
- user-researchSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 69
Every item needs a definition of done.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sprint Planner
Trigger
Activate on "plan sprint", "sprint planning", "what should we work on", "organize the backlog".
Behavior
Step 1: Get Input
Ask:
- Paste the backlog (titles, priorities, estimates)
- Team size
- Sprint duration (1 or 2 weeks)
- Any constraints or deadlines
Step 2: Plan
Sprint Goal (1 sentence)
Recommended Backlog | Item | Estimate | Priority | Dependencies | Owner |
Capacity Check
- Capacity: [X points/days]
- Planned: [total]
- Buffer (20%): [amount]
- Verdict: Over/Under/Right-sized
Stretch Goals (if team finishes early)
Risks to This Sprint
Example
Bad sprint plan (no capacity math, no priorities):
Sprint Goal: Work on stuff
Items: Auth, Dashboard, Bugs, API, DocsGood sprint plan:
Sprint Goal: Ship auth migration to 100% of web users
Capacity: 3 engineers x 10 days = 30 eng-days. At 80% = 24 available.
| Item | Estimate | Priority | Dependencies | Owner |
|------|----------|----------|-------------|-------|
| Auth migration: 40% → 100% rollout | 8d | P0 | QA sign-off (due Mon) | Jake |
| Mobile session bug fix | 5d | P0 | Root cause analysis (done) | Sarah |
| Dashboard loading perf | 3d | P1 | None | Alex |
| API rate limit docs | 2d | P2 | None | Jake |
Planned: 18 eng-days | Buffer: 6 eng-days | Verdict: Right-sized
Stretch Goals:
- Begin Outlook calendar sync research (3d) — only if auth ships by Thursday
Risks:
- Mobile bug fix estimate is uncertain. If root cause is deeper than
diagnosed, it could take 8d instead of 5d. Mitigation: Jake pairs
with platform team. If not resolved by Wednesday, descope and carry
to next sprint.Rules
- 80% capacity is the ceiling. Sprints loaded above 80% have a >50% chance of missing the goal.
- Flag items with unclear requirements. Unclear requirements are estimation landmines.
- Unresolved dependencies block sprint entry. Resolve before committing the item.
- Every item needs a definition of done.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.