rsaglobaltech/specgate
Specs as executable contracts: the daily loop as commands, the spec tree over MCP, the test before the code, and the gate as a hook that runs before the session can end.
Deliver one requirement: the test first, then the code, then the gate. Use when: A requirement — in spec.md or in an open change — has a real scenario and no implementation yet.
Merge a change into the spec tree once every requirement in it is applied. Use when: Every requirement the change adds or modifies is Implemented, and the person reviewing it says merge.
Run the gate: specs, links, coverage and the project's tests. Use when: After every change, and before saying the work is done.
Old name of /specgate:apply: deliver one requirement through the gate. Use when: Only when a script or a person asks for done — otherwise use /specgate:apply.
Turn the plan or brief into requirements, one module at a time. Use when: The project starts from a plan or brief (docs/brief.md), or the user names a module of it to specify.
See what is left, and the one command to run next. Use when: Starting work, or unsure what to do next.
Add one requirement straight to spec.md: its prose, its scenario and its row. Use when: A small project without changes, or the user asks for a single requirement outside a change.
Install spec-driven development on a repository that lacks it. Use when: The repository has code but no spec.md.
Open a change: the requirements to add or modify, as a reviewable delta. Use when: The user asks for a behaviour no requirement covers, or for a change to one that shipped.