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 workflow that extracts every requirement and converts it into an approved epic and story breakdown ready for developers. ## Core Features & Use Cases - Requirements Extraction: Scans PRD, Architecture, and UX design documents to inventory all functional requirements, non-functional requirements, and UX design requirements. - User-Value Epic Design: Groups requirements into standalone epics organized by user outcomes, with an FR coverage map guaranteeing nothing is missed. - Story Generation with Acceptance Criteria: Produces Given/When/Then acceptance criteria for each story, sized for a single dev agent and free of forward dependencies. - Use Case: After finishing a PRD and architecture for a new web app, run this workflow to produce a complete epics.md with validated coverage that a developer agent can implement story by story. ## Quick Start Ask the AI to create the epics and stories list from your PRD and architecture documents.