Spec Kit

Harden a spec-driven specification until its design is closed — no missing, ambiguous, or unverifiable design decisions remain. Runs an autonomous loop-until-dry under the /goal command: each round spawns a FRESH closed-design-enforcer sub-agent that detects net-new design gaps, which this skill deduplicates and logs into the spec's managed Design Gaps section, until a round finds nothing new. Then it runs a single human arbitration gate. Use this whenever the user wants to "close the design", "harden the spec", "find design gaps", "make the spec ready for cold execution", or before implementing any spec via implement-spec. Invoke proactively once a spec draft exists and before implementation begins.

Implement a closed spec file end-to-end, dispatching to the execution strategy that fits the work. Designed to run alongside the /goal command, which drives it non-stop until the spec is implemented, quality-reviewed, and verified to actually work. Acts as a pure dispatcher: it separates strategy selection from execution, choosing write-directly, agent-waves, or workflow based on scale and orchestration closure. Use after a spec's design is closed (via close-design) and the user wants it built. Trigger on "implement the spec", "build this spec", "execute the spec", or a /goal aimed at a spec file.

Create a new, closed and self-contained specification file optimized for Generative AI consumption and cold execution via the /goal command. Scaffolds the managed Design Gaps section that the close-design loop consumes. Use when the user wants to write a new spec, draft a specification, capture requirements, or plan a substantial change as a cold-executable spec.

Update an existing specification file optimized for Generative AI consumption, based on new requirements or code changes. Also the living-document maintainer for the spec-kit closure loop: folds accepted Design Gaps into the spec body and removes resolved entries from the managed section. Use when the spec drifted from the code, requirements changed, the implementation diverged, or the user says to sync, revise, or update the spec.