create-stories

Breaking epics into ready-to-implement stories involves parsing epic specifications, GDDs, governing ADRs, and the control manifest to generate structured story templates. Each template embeds traceable requirements, acceptance criteria, and test evidence paths for production readiness.

Epic to story generation is the process of transforming high-level epic specifications into a structured set of implementable story files. It embeds TR-ID, ADR guidance, acceptance criteria, story type, and test evidence paths directly into each generated story file.

To generate story templates from a GDD and ADRs, apply this Skill after creating epics. It reads the epic's Game Design Document and governing Architectural Decision Records to produce production-ready story templates with embedded traceability identifiers.

Yes, you need a control manifest to generate stories from epics. This Skill reads the control manifest alongside the epic's GDD and governing ADRs to ensure the generated story templates accurately reflect project constraints and traceable requirements.

When automating epic breakdown, generated story files are written to the production directory at production/epics/[epic-slug]/story-NNN-[slug].md. This structured output location enables seamless handoff to downstream implementation steps.

The best way to add traceable requirements to story files is by automating generation from governing ADRs and a control manifest. This embeds TR-IDs, ADR guidance, acceptance criteria, and test evidence paths directly into each story template.