moonspec-breakdown

Converting a technical design into user stories involves splitting broad Moon Spec designs into independent stories with explicit coverage ownership and acceptance criteria. This generates structured artifacts with stable DESIGN-REQ coverage mapping for planning and Jira export.

Design-to-story traceability maps each user story to stable DESIGN-REQ coverage points, preserving the original design reference for auditing. This ensures every requirement has explicit ownership and independent validation, reducing ambiguity in the backlog.

Generating a machine-readable backlog from a declarative design file requires running the breakdown workflow on pasted text or repository file paths. This outputs a stories.json file containing structured story candidates with clear acceptance criteria for downstream processing.

Exporting the generated story breakdown to Jira is supported through the structured story artifacts produced by the breakdown workflow. The output includes machine-readable stories.json and human-readable stories.md files designed for downstream specify, plan, and Jira export actions.

The story breakdown process works with both pasted technical design text and repository file paths. It processes declarative design documents directly and outputs the generated story candidates under the docs/tmp/story-breakdowns directory.

Design breakdown workflows for user story generation should not be used when working outside the Moon Spec framework or when the design lacks sufficient declarative detail. It requires broad, high-ambiguity design inputs to generate meaningful independent stories with stable coverage mapping.