What problem does it solve? Translating an approved Functional Requirements Specification into an actionable sprint backlog is error-prone: requirements get dropped, acceptance criteria stay vague, and out-of-scope items silently creep back in. This Skill produces a traceable, signature-gated Prioritized Backlog document where every story maps to a source requirement. ## Core Features & Use Cases - MoSCoW Prioritization: Organizes user stories into Must Have (Sprint 1-2), Should Have (Sprint 2-3), and a mandatory Won't v1 exclusion section with concrete deferral reasons. - Bidirectional Traceability: Vertical traceability maps every FR-XXX requirement to a story; horizontal traceability maps journey steps and screens (XD-J-XXX, XD-S-XXX) to stories, surfacing connective-tissue gaps like navigation and empty states. - Structured Acceptance Criteria: Enforces Given-When-Then scenarios per story, including at least one negative scenario, plus a global Definition of Done. - Use Case: After the FRS and Software Architecture Document are signed, a Product Owner runs this Skill to produce backlog.md with sprint assignments, dependency mapping, and a review checklist before requesting sign-off. ## Quick Start Ask the agent to generate the prioritized backlog for your project from the signed functional specification and architecture document, providing the FRS document ID, product owner name, and sprint velocity.
