BMAD Epics & Stories

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.

Scope Law (read first)

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.

Inputs (load these first)