What problem does it solve? Turning a raw or ambiguous feature request into a specification that a planner can act on requires structured discovery, ambiguity resolution, and traceability checks. This Skill guides that process inside a spec-kit project, producing a canonical spec contract and human-readable spec without writing implementation code. ## Core Features & Use Cases - Guided Requirement Discovery: Asks one high-impact question at a time, decomposes ambiguous terms, compares approaches, and confirms scope before writing artifacts. - Discussion Handoff Compilation: Validates a confirmed sp-discussion handoff contract and compiles it into a specification with semantic-delta tracking, avoiding repeated user review. - Deterministic Quality Gates: Runs self-review for placeholders, contradictions, dropped upstream signals, and missing acceptance proof before recommending the next workflow command. - Use Case: A user describes a new CLI feature in vague terms; the Skill clarifies scope, records semantic term decisions, writes spec-contract.json and spec.md, then routes to /sp.plan once planning-ready. ## Quick Start Invoke the skill with a description of the feature you want specified, such as asking it to specify a new command that scaffolds project templates.
