create-stories

To break epics into implementable stories with ADR traceability, decompose high-level epic designs into story-level tasks that map directly to GDD requirements and ADR decisions, ensuring governance and reproducible planning.

Converting high-level design documents into development tasks requires breaking epics into concrete, testable stories. This process enforces governance by consuming TR IDs and ADR decisions to generate ready-to-write story files for development.

When an ADR is in a Proposed state, you should mark related stories as blocked and surface gating conditions. This ADR governance integration prevents premature development until architectural decisions are finalized and approved.

Yes, generating stories from epics requires a control manifest to enforce governance rules. The process automatically associates TR-IDs from the registry and applies control-manifest rules during story generation to ensure traceable and compliant outputs.

Preparing story metadata for downstream QA readiness involves generating story files with evidence plans and metadata at the production/epics path. This facilitates subsequent story readiness checks and downstream validation processes.

Yes, you can map epic requirements directly to GDD specifications during decomposition. The process breaks epics into story-level tasks that explicitly align with GDD requirements and ADR decisions to maintain full traceability.