Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/sprint-plan
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.
Passed 15 of 19 test cases with the skill, and 4 of 19 without it.
and 15 more in the full report
13 fixed2 passed either way2 still failing2 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
After writing the sprint plan and status YAML to disk, what command should be suggested if stories were added beyond the original epic scope?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends running /scope-check command for scope creep validation | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,story_granularity,workflow
Resolved above — use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
!ls production/sprints/ 2>/dev/null || echo "(no production/sprints/ directory yet)"
Resolved before this skill runs — use it to identify the previous sprint in Phase 1 rather than re-globbing.
Extract the mode argument (new, update, or status).
See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
story_granularity — it sets how
many stories to allocate per sprint, scaled by velocity: 2–4 at coarse (the default, via rigor: minimal),
6–10 at balanced (rigor: standard), 15–25 at fine. A Ready backlog
smaller than the range is planned whole — never padded with invented stories.
Review mode check (before gates run):
--review overrides it
for this run) — do not re-resolve it, and do not ask for it. With nothing
configured it follows modes.rigor: solo at minimal, lean at standard.project.yaml, not to
production/review-mode.txt. modes.review_mode is one of the knobs
modes.rigor fronts: pinning it in project.yaml shadows the rigortest cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.