What problem does it solve? Teams often ship PRDs and specs that look complete but rest on unvalidated problems, vague requirements like "fast" or "user-friendly", and missing dependencies — leading to misaligned builds and rework. This Skill gates spec writing on a validated problem statement and enforces testable, measurable requirements. ## Core Features & Use Cases - Problem gating: Refuses to draft requirements until the problem statement has a clear problem, consequence, and goal grounded in evidence, or explicitly flags unvalidated assumptions. - PRD vs. spec selection: Distinguishes the what/why document (PRD) from the how document (spec) so the right artifact is written for the audience and moment. - Quality enforcement: Converts vague targets into measurable requirements, rewrites task-style user stories into value-based INVEST stories, and adds a Dependencies, Constraints & Assumptions section. - Use Case: Ask it to write a PRD for a new onboarding flow; it will first push you to pin down the problem with evidence, then produce a spec with testable requirements, explicit out-of-scope items, and flagged risks. ## Quick Start Ask the assistant to write a PRD for your feature idea, or paste an existing spec and ask it to review the requirements for testability and missing risks.
