What problem does it solve? After stakeholders sign off on a PRD, teams still face the hard work of turning validated intent into an executable plan: deciding what is dev-ready, where the MVP cut-line falls, how work is sequenced by risk, and how epics and tickets get created. This Skill structures that transition so planning sessions produce a committed increment instead of relitigating scope. ## Core Features & Use Cases - Readiness Gating: Verifies design (Design Signal 90) and architecture (tech spec, spikes, ADRs) are dev-ready with named evidence, converting gaps into first-sequence items. - MVP Cut-Line & Sequencing: Draws the cut-line on a story map against PRD success criteria, assigns below-the-line work to named releases, and orders work by dependency and risk. - Ticket Cutting & Commitment: Creates epics and tickets with Gherkin acceptance criteria and PRD traceability, marks the PRD Commitment-Ready, and books the release-readiness review. - Use Case: After Sign-Off 2 on a checkout redesign PRD, run this Skill to produce docs/product/pi/checkout-increment.md with readiness verdicts, a committed MVP slice, and tracker tickets linked back to PRD sections. ## Quick Start Use the pi-planning skill to turn our signed-off PRD into a committed increment plan with an MVP cut-line, sequenced epics, and tickets.
