What problem does it solve? Product requirements documents often contain large, ambiguous feature descriptions that developers cannot estimate or test directly. This Skill breaks PRD functionality into small, independently deliverable user stories with concrete acceptance criteria, giving teams a shared definition of done before a sprint starts. ## Core Features & Use Cases - INVEST Validation: Checks every story against the six INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) so stories stay sprint-sized and estimable. - Given/When/Then Acceptance Criteria: Generates multiple scenarios per story including normal paths and edge cases such as empty states, missing permissions, and duplicate submissions. - Epic/Feature/Story Hierarchy: Organizes large features into a three-level story map with priority (P0/P1/P2), complexity (S/M/L), and hour estimates aligned to WBS estimation. - Use Case: After a PRD for a property listing platform is approved, use this Skill to split the "property search" feature into stories like state filtering, each with scenarios for normal filtering, no results, and multi-select behavior. ## Quick Start Break down the approved PRD for the property management module into INVEST-compliant user stories with Given/When/Then acceptance criteria for sprint planning.
