create-speclisted

# Engineering Spec When this skill is activated, produce a `docs/SPEC.md` that fully defines what needs to be built, why, and under what constraints. This is a pre-implementation document — its purpose is to surface ambiguity, align stakeholders, and give engineers a single source of truth before work begins. **When to use this skill vs. related ones:** - **this skill (`create-spec`)** — defines the *what* and *why*: requirements, constraints, scope, success criteria. Run it first. - `create-architecture-proposal` — defines *system-wide* architecture (bounded contexts, layering) once requirements are known. - `create-design-proposal` — defines the *how* for a single feature. For component-level interface contracts and per-component test design, defer to it rather than duplicating that depth here. ## Clarifying Questions Ask the questions in **three rounds**. Do not dump all questions at once. Wait for the answers to each round before proceeding to the next. --- ### Round 1 — Purpose & Scope **Always ask all of these. Never skip or infer.** 1. What are we building? One sentence, present tense: "A service that…", "A CLI tool that…", "A module that…" 2. What problem does it solve? Who has this problem today, and how are they currently working around it? 3. Who are the primary users or consumers — humans, other services, or both? Describe each type briefly. 4. List the 5–10 most important things the system must be able to DO (functional requirements). Just bullet points —