create-stories

To break down an epic into actionable game development stories, use an automated decomposition process that parses epic docs, GDD requirements, governing ADRs, and the control manifest to generate production-ready story artifacts with TR-IDs and acceptance criteria.

Epic decomposition in a game development workflow is the process of parsing a single epic alongside GDD requirements and ADRs to produce implementable story files mapped with TR-IDs, acceptance criteria, and test evidence paths.

Yes, you need existing ADRs and a control manifest to generate story files, because the process validates ADR existence and embeds ADR decisions to enforce governance before creating the stories.

ADR governance applies to generated story artifacts by embedding ADR decisions directly into the stories, validating ADR existence before creation, and ensuring TR-ID mapping aligns with the control manifest.

The best way to map TR-IDs for game development epics is to automate TR-ID mapping during story generation, ensuring each output story file in the production/epics directory contains traceable references to GDD requirements.

You should not use automated epic decomposition when your epic lacks governing ADRs or a validated control manifest, as the process requires these inputs to enforce governance and map TR-IDs correctly.