What problem does it solve? When implementing features from a spec, ticket, or PRD, requirements get silently dropped, half-built, or quietly abandoned when they turn out to be hard — and unrequested scope creep sneaks in. This Skill enforces a systematic four-phase verification workflow so nothing is missed and nothing extra is built before declaring work done. ## Core Features & Use Cases - Requirement Decomposition: Turns any spec into a numbered checklist of atomic requirements, including implied requirements, edge cases, error states, permission boundaries, and explicit out-of-scope items. - Acceptance Criteria Extraction: Distinguishes what a feature does from how to know it is done correctly, hunting for unstated criteria around failures, empty states, and third-party dependency behavior. - Diff-Based Verification: Re-reads the checklist against the actual diff to catch partial implementations, abandoned requirements, and scope creep, producing a pass/fail readout per item. - Ambiguity Handling: Flags ambiguous spec points with a decision rule for when to ask the user versus when to default, with batched-question phrasing examples. - Use Case: Before marking a ticket complete, run the checklist against the diff to confirm every requirement — including the implied cascading cleanup and error handling the ticket never spelled out — is actually implemented. ## Quick Start Check this implementation against the spec in the ticket and verify all requirements are covered before marking it done.
