What problem does it solve? Turning a PRD and architecture document into an actionable backlog is slow and error-prone: requirements get missed, epics get organized by technical layers instead of user value, and stories lack testable acceptance criteria. This Skill guides a structured, step-by-step decomposition so every requirement maps to a story a developer can implement. ## Core Features & Use Cases - Requirements Extraction: Validates and extracts functional requirements, non-functional requirements, architecture constraints, and UX design requirements from PRD, Architecture, and UX documents. - Epic Design with Coverage Mapping: Organizes requirements into user-value-focused epics and produces an FR coverage map so no requirement is left unassigned. - Story Generation with Acceptance Criteria: Creates Given/When/Then acceptance criteria for each story, sized for a single dev agent, with dependency validation across epics and stories. - Use Case: After finishing a PRD and architecture for a new product, run this workflow to produce a complete epics.md with validated epics, stories, and acceptance criteria ready to hand to a developer agent. ## Quick Start Ask the assistant to create the epics and stories list from your PRD and architecture documents.