Specbridge

SpecBridge

An open, model-agnostic spec runtime for existing Kiro projects.

**No conversion. No duplicated specs. No lock-in.**

Start in Kiro. Continue anywhere. Return whenever you want.

existing .kiro specs
        ↓
approve requirements, design, and tasks
        ↓
implement with Claude Code / Codex / Gemini
        ↓
capture real Git evidence
        ↓
verify spec drift locally and in CI
        ↓
extend with templates and extensions

30-second start in any project that already contains `.kiro/`:

npm install -g specbridge-cli
specbridge doctor
specbridge spec list
specbridge spec verify --changed

Using Claude Code? Install the self-contained plugin instead: `/plugin marketplace add HelloThisWorld/specbridge` → `/plugin install specbridge@specbridge-plugins` — [details](docs/getting-started/claude-code-plugin.md).

[](https://github.com/HelloThisWorld/specbridge/actions/workflows/ci.yml) [](https://github.com/HelloThisWorld/agent-skill-verification-template) [](LICENSE)

**[Documentation hub](docs/README.md)** · **[Releases](https://github.com/HelloThisWorld/specbridge/releases)**

Maturity, honestly: v1.0.0 has a deterministic, offline core (parsing, approvals, verification, evidence) with stable public contracts, while model-assisted parts remain inherently nondeterministic, extensions run out of process but are not OS-sandboxed, and release binaries are unsigned — see [SECURITY.md](SECURITY.md) and the [threat model](docs/security/threat-model.md).

SpecBridge is an independent open-source project, **not affiliated with, endorsed by, or sponsored by AWS or Kiro** — see [NOTICE.md](NOTICE.md).

---

Why this exists

Kiro popularized a great idea: spec-driven developme