create-stories

To decompose epics into actionable developer stories, you generate story-level files that include specific acceptance criteria, test-evidence paths, and governing ADRs for traceability. This breaks down high-level requirements into implementable tasks.

Linking ADR governance and TR-ID references to development stories is achieved by generating story files that explicitly map each task to its governing ADR and TR reference, ensuring full traceability for audits and architectural reviews.

Generating story files in dependency order from a single epic involves processing the epic to output implementable markdown files under a specific epic directory, sequenced so developers can execute tasks in the correct progression.

Yes, you need to create epics before generating story files because the story decomposition process runs after epic creation to consume the epic slug and produce the downstream story-level tasks required by developers.

Yes, you can include test-evidence paths within acceptance criteria because the story decomposition process explicitly ensures each generated story file contains its acceptance criteria alongside the required test-evidence path for validation.