create-epics-and-stories

Decomposing product requirements into epics and stories involves mapping PRD, architecture, and UX artifacts into structured work items with clear acceptance criteria and frontmatter-tracked progress to ensure complete coverage of FRs, NFRs, and UX considerations.

Breaking down product requirements for organized development planning is best achieved through a step-file driven workflow with strict sequential execution, ensuring each epic and story is user-value oriented and independently deliverable with consistent formatting.

Yes, you can map non-functional requirements and UX constraints into development stories. The workflow generates epic and story artifacts from FRs, NFRs, and UX inputs, ensuring complete coverage by architecture constraints and UX considerations with interactive validation.

You track progress and maintain iterative refinement when creating epics and stories by using frontmatter-based progress tracking and persistent facts within the generated artifacts, applying templates and conventions that ensure consistent formatting and documentation.

You do not strictly need a PRD to start, but you must validate prerequisites and extract requirements in the first step. The workflow applies to PRD, architecture, and UX artifacts, generating structured epics and stories from available FRs, NFRs, and UX inputs.

Interactive validation when mapping requirements to epics works through approval loops that align the generated stories with your product strategy, verifying that each work item is user-value oriented and independently deliverable before activation.