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 a complete epic and story breakdown ready for developers. ## Core Features & Use Cases - Requirements Extraction: Systematically pulls functional requirements (FRs), non-functional requirements (NFRs), architecture constraints, and UX design requirements from PRD, Architecture, and UX documents. - User-Value Epic Design: Collaboratively designs epics organized by user outcomes rather than technical layers, with a full FR-to-epic coverage map. - Story Generation with Acceptance Criteria: Produces stories in As a/I want/So that format with Given/When/Then acceptance criteria, sized for a single developer session and free of forward dependencies. - Use Case: After finishing a PRD and architecture spec for a new product, run this workflow to produce a validated epics.md document where every requirement maps to at least one implementable story. ## Quick Start Ask the AI to create the epics and stories list from your PRD and architecture documents.
