What problem does it solve? Turning a long discussion or scattered repository context into a structured, reviewable specification is time-consuming and error-prone. This Skill converts the current conversation and repo evidence into a concise Markdown draft spec, clearly separating facts, decisions, assumptions, and open questions. ## Core Features & Use Cases - Structured spec drafting: Produces sections for problem statement, goals, user stories, requirements, acceptance criteria, and risks, following a supplied template when available. - Evidence grounding: Labels facts versus assumptions, links claims to inspected repository paths or symbols, and asks for missing inputs instead of guessing. - Draft-only safety boundary: Never publishes to issue trackers, creates labels, or modifies repository files; publication is treated as a separate authorized task. - Use Case: After a design discussion about a new feature, ask for a spec draft and receive a review-ready PRD with observable acceptance criteria and explicit open questions. ## Quick Start Ask the assistant to use draft-spec to turn the current discussion into a review-ready Markdown specification without publishing it.
