Agent skill · operations · borghei
sprint-plan
Plan a sprint that ships — capacity, commitment vs stretch, dependencies, and risk identification that prevents mid-sprint surprises. Use to build the sprint planning artifact itself.
Why this skill is useful
Provides a structured sprint planning workflow that includes capacity calculations, risk identification, and dependency management, which the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Sprint Planning A sprint plan that survives contact with reality. Covers capacity math, commit vs stretch separation, dependency identification, and the pre-sprint review that prevents mid-sprint surprises. When to use this skill Sprint kickoff (every 1-3 weeks) Sprint-plan template for new teams Sprint-plan audit when sprints consistently miss Quarter-start planning (rolled up across sprints) Post-mortem on a missed sprint (gap analysis) The 7 sprint-plan elements 1. Sprint goal — one sentence: what this sprint exists to achieve 2. Team capacity — actual hours / story points after PTO, on-call, etc. 3. Commits — items the team confidently ships 4. Stretch — items if everything goes well; nothing depends on 5. Dependencies — what must happen by when (external + internal) 6. Risks — what could derail; mitigation per risk 7. Definition of done — when is each item "done"? Clarify First Before generating the sprint plan, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Sprint goal — the one-sentence outcome this sprint exists to achieve (element 1; lets you scope and say no to off-goal asks) [ ] Real team capacity — working days minus PTO/on-call/meetings/interrupts × focus factor (element 2; sizes the commit and prevents the 100%-fill miss) [ ] Backlog readiness — are candidate items refined, estimated, and ≤5 days (unrefined items are ineligible and blow estimates mid-sprint) [ ] Known dependencies — cross-team/external blockers with owners (element 5; unconfirmed assumptions become mid-sprint crises) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/sprint-plan