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. ## Core Features & Use Cases - Requirements Extraction: Scans PRD, Architecture, and UX Design documents to extract functional requirements, non-functional requirements, and UX design requirements into a coverage map. - Collaborative Epic Design: Groups requirements into user-value-focused epics with explicit FR coverage mapping and user approval gates. - 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 dev agent. - Final Validation: Verifies full FR coverage, story independence, and dependency ordering before completion. - Use Case: After finishing a PRD for a task management API, run this Skill to produce an epics.md file where every requirement maps to an approved epic and implementable story ready for sprint planning. ## Quick Start Ask the agent to create the epics and stories list from your PRD and architecture documents.
