Agent skill · product strategy · 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. Use when the user says "sequence the stories", "build the sprint status", "plan the waves", "create sprint-status.yaml", "assign parallel sets", "order stories by dependency", "what can run in parallel", "set up story sequencing", "initialize sprint tracking", "ready the backlog", or "prepare for dev handoff". Also triggers on "sprint planning" when the project already has epics defined. SCOPE: SEQUENCING AND ORCHESTRATION ONLY. No velocity, no burndown, no committed points, no coverage metrics. Capacity is expressed as wave width (concurrent story count), not points. The final artifact is a ready-for-dev handoff manifest; implementation is delegated to external dev tools.
Why this skill is useful
Adds specific scripts for initializing and sequencing sprint status that are not commonly found in public documentation.
What it needs
Requires bash installed locally. About 4k tokens when loaded. Last updated 2026-06-20. 471 stars on the source repository.
What this skill does
BMAD Sprint Planning Role: Sequencing & Handoff Bridge — Phase 4 orchestration System-of-record: bmad-output/sprint-status.yaml --- What This Skill Does 1. Reads planning artifacts (PRD, architecture, epics, stories) from bmad-output/. 2. Derives a dependency graph across all stories. 3. Assigns each story a parallelset (wave) — stories in the same wave have no mutual dependencies and can run concurrently. 4. Emits bmad-output/sprint-status.yaml using the canonical template. 5. Marks the first wave of stories ready-for-dev; all others remain backlog. 6. Optionally re-sequences on demand as stories are completed or new ones are added. This skill does not write application code, run tests, lint, build, or review diffs. --- Three-Intent Operation 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 --- Workflow — Create 1. Load planning artifacts Priority order: epics.md → prd.md → architecture.md → individual story files. 2. Extract epics and stories Parse all story IDs: format {epic}.{story}.{slug}.story.md (e.g., 2.1.stripe-integration.story.md) Derive epic ordering from the epic list in epics.md or prd.md 3. Build dependency graph Read dependencies[] from each story's frontmatter or Dev Notes section Topological sort: stories with no unmet dependencies → wave 1; stories unblocked after wave 1 → wave 2; etc. 4. Initialize sprint-status.yaml Then populate with sequenced data (see template). 5. Sequence stories 6. Set initial statuses Wave 1 stories: status: ready-for-dev All other stories: status: backlog Epics: status: in-progress if any child story is ready-for-dev; else backlog 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/bmad-sprint-planning