Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-epics-and-stories
Solutioning flagship — shards a PRD + architecture into epics.md and individual {epic}.{story}.{slug}.story.md context objects, the LAST planning artifact before external dev handoff. Each story is a self-contained ~8K-token compiled context object: Dev Notes with SOURCE CITATIONS back to prd.md/architecture.md, Acceptance Criteria, Tasks/Subtasks mapped to ACs, Testing strategy, Dependency Maps, an explicit Owned File/Module Scope list (the lever for parallel-conflict-free scheduling), and Lear
Passed 12 of 19 test cases with the skill, and 5 of 19 without it.
and 6 more in the full report
9 fixed5 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Story 1.2 in our planning folder is marked ready-for-dev with complete acceptance criteria and scope. Please write the React component implementation in src/components/Auth.tsx to satisfy these requirements.
| Checked | Without skill | With skill |
|---|---|---|
| Declines writing application source code | Missed | Passed |
The instructions your model reads when the skill loads.
Track-adaptive sharding. Turn approved planning docs into the executable backlog: one
epics.md map plus per-story context objects. This is the final planning step — the next
thing that touches a story is an external dev tool, not this plugin.
Persona flavor: the Architect (Winston) shards; the PM (John) confirms scope. Lightweight flavor only — this is a workflow.
This skill PLANS. It NEVER writes application code, runs tests, lints, checks coverage, or
builds. The last artifact it emits is a story file marked status: ready-for-dev. Acceptance
Criteria, a Testing strategy, and Dev Notes are planning outputs you author. Executing
tests or writing implementation is out of scope — plan it and hand it off. If tempted to
"implement" or "run the suite", STOP.
| File | Why |
|---|---|
bmad-output/project-context.md | Project constitution — load every run |
bmad-output/prd.md | Functional requirements, epic intent |
bmad-output/architecture.md | Tech stack, components, module boundaries |
bmad-output/ux-design.md (if present) | UI acceptance details |
bmad-output/decision-log.md | Threaded decisions to honor |
existing bmad-output/stories/*.story.md | Learnings + ID continuity |
Output folder default: bmad-output/ (honor user override). Stories go in
bmad-output/stories/, the map in bmad-output/epics.md.
epics.md, then compile story files.Ask which intent if ambiguous. Do not silently regenerate existing stories.
test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.