create-stories

To break epics into actionable developer stories, decompose Foundation and Core epics by reading the epic's GDD, governing ADRs, and control manifest to ensure traceability. The process outputs individual story files in proper dependency order for sequential implementation.

Epic traceability in project management ensures each developer story maps directly to GDD requirements and ADR guidance. It links high-level epics to implementation tasks by using a TR-registry to map acceptance criteria and constraints to the generated stories.

Yes, you need all referenced ADRs to exist on disk before generating stories from epics. The story generation process reads governing ADRs alongside the GDD and control manifest to ensure every output story adheres to established architectural decisions.

Generated stories are saved as Markdown files using the naming convention story-NNN-[slug].md. They are organized within the .ags/project/epics/[epic-slug]/ directory structure to maintain project organization and dependency order.

To prepare epics for story generation, run the /create-epics workflow first to generate the foundation and core epics. Once epics are established, you can run /create-stories on a chosen epic slug to produce the initial implementable story set.

After epic story generation, the workflow proceeds to /story-readiness and /dev-story. These downstream workflows take the generated story files and evaluate their implementation readiness before passing them to the development team.