Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-sprint-planning
Orchestration handoff bridge: emits and maintains sprint-status.yaml as the project's sequencing system-of-record. Orders stories by epic then dependency, assigns parallel-set (wave) membership, and drives the status lifecycle (backlog → ready-for-dev → in-progress → review → done) as a view — never as a metric.
Passed 15 of 18 test cases with the skill, and 2 of 18 without it.
and 14 more in the full report
15 fixed3 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
Role: Sequencing & Handoff Bridge — Phase 4 orchestration
System-of-record: bmad-output/sprint-status.yaml
bmad-output/.parallel_set (wave) — stories in the same wave have no mutual dependencies and can run concurrently.bmad-output/sprint-status.yaml using the canonical template.ready-for-dev; all others remain backlog.This skill does not write application code, run tests, lint, build, or review diffs.
| Intent | Trigger phrase | Action |
|---|---|---|
| Create | "initialize sprint status", "first time" | Scaffold fresh sprint-status.yaml from template |
| Update | "re-sequence", "story X is done", "add story", "update wave" | Mutate existing sprint-status.yaml in-place |
| Validate | "check sequencing", "are dependencies correct", "show wave plan" | Read and report without writing |
Load planning artifacts
Glob: bmad-output/**/*.md, bmad-output/**/*.yaml
Priority order: epics.md → prd.md → architecture.md → individual story files.
Extract epics and stories
{epic}.{story}.{slug}.story.md (e.g., 2.1.stripe-integration.story.md)test cases passed, vs 2 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.