claudegoodies
Skill

sprint-plan

From Donchitos

Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.

Generates or updates a sprint plan and status YAML from milestone, backlog, and risk-register files.

Use it when

  • Starting a new sprint and need tasks pulled from design/gdd backlog
  • Updating an in-progress sprint's story list or estimates
  • Checking sprint burndown and blocker status mid-sprint

Skip it if

  • Requires a specific production/ folder structure (milestones, sprints, gdd, risk-register)
  • Tied into a broader director-gate/QA review workflow, not standalone
  • Not useful if you don't track sprints as markdown/yaml files

Facts

Status
Actively maintained
Last commit
Declared tools
Read, Glob, Grep, Write, Edit, Task, AskUserQuestion
Model
sonnet

Source preview

The instructions Claude Code reads when this skill runs.

## Phase 0: Parse Arguments

Extract the mode argument (`new`, `update`, or `status`) and resolve the review mode (once, store for all gate spawns this run):
1. If `--review [full|lean|solo]` was passed → use that
2. Else read `production/review-mode.txt` → use that value
3. Else → default to `lean`

See `.claude/docs/director-gates.md` for the full check pattern.

**Review mode check** (before gates run):
- Read `production/review-mode.txt` if it exists. Use that mode.
- If the file doesn't exist and this is a `new` sprint: use `AskUserQuestion`:
  - Prompt: "No review mode is set. Which review depth would you like for this sprint?"
  - Options:
    - `[A] full — spawn all director and lead gates`
    - `[B] lean — skip non-phase-gate director reviews (recommended for most sprints)`
    - `[C] solo — skip all gate spawning`
  - After selection: write `production/review-mode.txt` with the chosen mode. Say: "Review mode set to [mode] and saved to production/review-mode.txt."
- If the file doesn't exist and this is NOT a `new` sprint (e.g., updating an existing sprint): default to `lean` silently.

---

## Phase 1: Gather Context

1. **Read the current milestone** from `production/milestones/`.

2. **Read the previous sprint** (if any) from `production/sprints/` to
   understand velocity and carryover.

3. **Scan design documents** in `design/gdd/` for features tagged as ready
  
View full source on GitHub →

Other skills