![\"OpenSplx](\"assets/opensplx_pixel_light.svg\"){kind=tracking}
\n \n \n \n
Spec-driven development for AI coding assistants.
\n\n ![\"Fork](\"https://img.shields.io/badge/Fork%20of-OpenSpec-blue?style=flat-square\"){kind=icon}
![\"node](\"https://img.shields.io/node/v/@fission-ai/openspec?style=flat-square\")
![\"License:](\"https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square\"){kind=icon}
\n
\n ![\"OpenSplx](\"assets/openspec_dashboard.png\")
\n
\n Follow @0xTab on X for updates · Join the OpenSpec Discord for help and questions.\n
\n\n# OpenSpec\n\nOpenSpec aligns humans and AI coding assistants with spec-driven development so you agree on what to build before any code is written. **No API keys required.**\n\n## Why OpenSpec?\n\nAI coding assistants are powerful but unpredictable when requirements live in chat history. OpenSpec adds a lightweight specification workflow that locks intent before implementation, giving you deterministic, reviewable outputs.\n\nKey outcomes:\n- Human and AI stakeholders agree on specs before work begins.\n- Structured change folders (proposals, tasks, and spec updates) keep scope explicit and auditable.\n- Shared visibility into what's proposed, active, or archived.\n- Works with the AI tools you already use: custom slash commands where supported, context rules everywhere else.\n\n## How OpenSpec compares (at a glance)\n\n- **Lightweight**: simple workflow, no API keys, minimal setup.\n- **Brownfield-first**: works great beyond 0→1. OpenSpec separates the source of truth from proposals: `openspec/specs/` (current truth) and `openspec/changes/` (proposed updates). This keeps diffs explicit and manageable across features.\n- **Change tracking**: proposals, tasks, and spec deltas live together; archiving merges the approved updates back into specs.\n- **Compared to spec-kit & Kiro**: those shine for brand-new features (0→1). OpenSpec also excels when modifying existing behavior (1→n), especially when updates span multiple specs.\n\nSee the full comparison in [How OpenSpec Compares](#how-openspec-compares).\n\n## How It Works\n\n```\n┌────────────────────┐\n│ Draft Change │\n│ Proposal │\n└────────┬───────────┘\n │ share intent with your AI\n ▼\n┌────────────────────┐\n│ Review & Align │\n│ (edit specs/tasks) │◀──── feedback loop ──────┐\n└────────┬───────────┘ │\n │ approved plan │\n ▼ │\n┌────────────────────┐ │\n│ Implement Tasks │──────────────────────────┘\n│ (AI writes code) │\n└────────┬───────────┘\n │ ship the change\n ▼\n┌────────────────────┐\n│ Archive & Update │\n│ Specs (source) │\n└────────────────────┘\n\n1. Draft a change proposal that captures the spec updates you want.\n2. Review the proposal with your AI assistant until everyone agrees.\n3. Implement tasks that reference the agreed specs.\n4. Archive the change to merge the approved updates back into the source-of-truth specs.\n```\n\n## Getting Started\n\n### Supported AI Tools\n\n