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, four-step workflow that extracts every requirement and converts it into a validated 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 outcome, with a full FR-to-epic coverage map and file-churn consolidation checks. - Story Generation with Acceptance Criteria: Produces developer-ready stories in Given/When/Then format, sized for a single dev agent and free of forward dependencies. - Use Case: After finishing your PRD and architecture docs, run this workflow to produce a complete epics.md where every FR, NFR, and UX requirement maps to at least one validated story. ## Quick Start Ask the agent to create the epics and stories list from your PRD and architecture documents.
