How do I plan a sprint?
Sprint planning operates on the current sprint document and the product backlog. For automated orchestration, use the agile-plan-sprint skill. For general backlog housekeeping without sprint selection, use How do I refine the backlog? first.
Question
How do I plan a sprint — set its mission, score backlog candidates against it, and promote selected captures into stories?
Answer
Open the current sprint document and confirm or set the mission:
./projects/ores.compass/compass.sh list --type sprint --sort path | tail -3
The
* Missionmust be a single sentence before scoring can proceed. If it reads(One sentence — what this sprint exists to achieve.)it is unset — agree on it with the user now.- Note what is already committed — read the sprint's
* Storiestable. STARTED and BACKLOG stories are already in scope; do not re-select them. List next-bucket candidates:
./projects/ores.compass/compass.sh next
Score each candidate on three axes — record results as a table before presenting to the user:
Criterion Scoring guidance Fit Direct mission advance = high; tangential = low Size One sprint / one story = high; multi-sprint = low Ready No blockers, no unresolved dependencies = high - Present the ranked candidates and get the user's confirmation on which to promote. Sprint scope is always the user's decision.
Promote each confirmed capture to a story:
a. Scaffold the story in the sprint folder, preserving the capture's
:ID:with--id. Usecompass add— it defaults--parent-dirto the current sprint automatically:projects/ores.compass/compass.sh add story \ --slug <slug> \ --id <capture-uuid> \ --title "<title>" --description "<description>"
Pass
--parent-dir doc/agile/versions/v0/sprint_NNexplicitly only if the story belongs to a sprint other than the current one.b. Remove the capture from the backlog:
git rm doc/agile/product_backlog/next/<slug>.org
c. Fill in the story's
* Goal,* Acceptance, and at least one task skeleton.Add each promoted story to the sprint's
* Storiestable:| [[id:<uuid>][<title>]] | BACKLOG | YYYY-MM-DD | | <one-line theme> |
Commit:
git add doc/agile/versions/v0/sprint_NN/ \ doc/agile/product_backlog/ \ doc/agile/versions/v0/sprint_NN/sprint.org git commit -m "[agile] Sprint NN — promote N stories from backlog"
After planning, use How do I start work on a story? to move the first story from BACKLOG → STARTED and create its feature branch.
Script
No single script — the agile-plan-sprint Claude Code skill orchestrates this procedure interactively.
Tested by
Manual. Run once per sprint, at the start of the planning phase.
See also
- Sprint planner — Claude Code skill for this procedure.
- How do I refine the backlog? — run before planning to ensure candidates are clean.
- How do I start work on a story? — next step after planning.
- How do I open a new sprint? — use this first if the sprint has not been scaffolded yet.
- How do I add a doc with compass? — preferred way to create stories and tasks.
- How do I create a new doc? — full codegen reference for all doc types.