What problem does it solve?
This Skill turns high-level epics, GDD requirements, and governing ADRs into a prioritized set of traceable, developer-ready story files so engineering teams can pick up well-scoped work without ambiguity or rework.
Core Features & Use Cases
- Automated decomposition: Reads an epic, its GDD, referenced ADRs, control manifest rules, and TR-ID registry to decompose acceptance criteria into discrete stories.
- Governance & validation: Confirms ADR existence, embeds ADR guidance and engine risk, and blocks work when required artifacts are missing or Proposed ADRs are present.
- QA integration: Classifies story types, requests QA Lead readiness gates in full review mode, and embeds QA test cases and test evidence requirements into each story file.
- Use Case: Product owners and lead programmers run this after creating epics to produce production/epics/[epic-slug]/story-NNN-[slug].md files with ready-to-implement acceptance criteria and QA specs.
Quick Start
Run the skill by issuing /create-stories [epic-slug] to generate a full set of story markdown files for that epic.