Shape the work
OpenSpec, Spec Kit, Superpowers, Markdown, and custom docs stay useful as authoring systems.
Spec governance for AI coding agents
Approve one version.
Verify the build.
Give coding agents approved context, then review delivery evidence against the same acceptance criteria.
WI-101 / audit-log permissions
Reviewing…
Acceptance criteria / evidence
- Admins can view permission-change events
- Member roles cannot read restricted payloads
- Tests cover allow and deny paths
tests
types
lint
delivery review / per-criterion evidence
Keep the tools that already shape and ship your work.
CLI and IDE handoff
Experimental tracker mirrors
The supported alpha path is CLI-first. Tracker connectors mirror status one way.
The governed loop in three moves.
SpecGate does not replace your spec tool, tracker, or IDE. It makes the handoff explicit, then checks the finished work against the approved contract.
-
Publish
Bring any spec format
OpenSpec, Spec Kit, Superpowers, a quick change note, or your own document set. You declare the document roles and SpecGate resolves the automatic policy.
-
Hand off
Approve one Context Pack
The coding agent gets the approved version, acceptance criteria, non-goals, risks, tasks, and applicable Skills through the CLI.
-
Review
Review delivery evidence
SpecGate compares completion claims, tests, docs, and changed files against every acceptance criterion before you close the work.
See it run, command by command.
The CLI is the supported alpha path. Use it directly, or let Cursor, Claude Code, or Codex pull the same Context Pack and report evidence.
$ specgate artifact publish --file artifact.json --preview Artifact publish preview: docs/spec.md spec 4821 bytes No publication performed: Human confirmation required before publishing. $ specgate artifact publish --file artifact.json Published 8a42… $ specgate gates check <artifact-id> Spec quality: passed $ specgate --yes artifact approve <artifact-id> Approved 8a42… (v1)
Approve the contract. Publish immutable documents, run readiness, then record the human decision.
Keep your stack. Add the governed handoff.
SpecGate connects planning and implementation. Author where you already work, approve one version, then review the delivery against it.
Run execution
Issues, sprints, code changes, PRs, and day-to-day collaboration stay in your existing stack.
Own the governed handoff
Versioned approval, readiness gates, Context Packs, delivery review, and evidence trust live here.
- Approved spec versions
- Readiness gates
- Context Pack handoff
- Delivery review verdicts
Experimental connectors mirror tracker status into SpecGate. Your tracker does not become a second spec source.
What teams ask first.
How is this different from spec tools?
Spec tools help shape work. SpecGate versions the result, runs readiness gates, hands one approved Context Pack to the coding agent, and reviews delivery evidence against it.
What spec formats do you accept?
Bring an OpenSpec, Spec Kit, or Superpowers project, Markdown, or your own document set. You explicitly map each document to a role and SpecGate resolves the automatic policy.
Do we have to leave our coding agent?
No. Cursor, Claude Code, Codex, or a human can use the CLI. The agent reads the Context Pack before coding and reports evidence after implementation.
Do I need an LLM API key?
No. The deterministic core works without a model. Configure one only when you want independent model-backed readiness or delivery judgment.
What does the delivery review check?
Each acceptance criterion is checked against reported evidence and automated checks such as tests, types, and lint. Failed criteria stay visible for the next handoff.
Close the loop on agent delivery.
The local-first default uses no Docker or server. Hand off approved context and review the evidence that comes back.