SpecWeave
The spec-driven framework for AI coding agents. First-class support for Claude Code — compatible with any LLM-powered coding tool.
Coordinate parallel AI agents. Prevent task overlap. Quality gates. Ship features while you sleep.
npm install -g specweave # Requires Node.js 20.12.0+
Quick Demo
/sw:increment "User authentication" # AI creates spec + plan + tasks
/sw:auto # Autonomous execution for hours
/sw:grill 0001 # Senior-level code review
/sw:done 0001 # Validate and complete
What happens: Claude creates a full specification, executes tasks autonomously, runs tests, fixes failures, and syncs progress to GitHub/JIRA. You review finished work.
Why SpecWeave?
AI coding agents are powerful individually. Run three of them on the same codebase and you get conflicts, duplicated work, and zero traceability.
SpecWeave solves this with file-based coordination:
.specweave/increments/0001-oauth/
├── spec.md ← WHAT: User stories, acceptance criteria
├── plan.md ← HOW: Architecture decisions, tech choices
└── tasks.md ← DO: Implementation tasks with tests
Each increment is a self-contained scope. Each agent knows exactly what's taken and what's available. No overlap. No conflicts. Six months later, search "OAuth" and find exactly what was decided, who approved it, and why.
What Makes It Different
- Parallel agent coordination — multiple Claude Code sessions, OpenClaw instances, or remote agents work on different increments without stepping on each other.
- Autonomous execution — runs for hours, not minutes. Write, test, fix, repeat.
- Persistent memory — AI learns from corrections. Fix once, remembered permanently.
- Quality gates — Code Grill reviews code like a demanding senior engineer before every release.
- Living documentation — specs, ADRs, and runbooks sync automatically after every task.
- 100+ specialized skills — PM, Architect, QA, Security, DevOps, Frontend, Mobile, ML, and more collaborate on deliverables.
- External sync — GitHub Issues, JIRA, Azure DevOps — bidirectional, real-time.
- Self-improving — captures what works and what doesn't. Gets smarter over time.
- LSP integration — semantic code intelligence for TypeScript, Python, Go, Rust, Java, C#.
Install
npm install -g specweave
cd your-project
specweave init .
Then in Claude Code:
/sw:increment "Add dark mode" # Describe your feature
/sw:auto # Ship while you sleep
Node.js 20.12.0+ required (22 LTS recommended). Getting
SyntaxError? Upgrade instructions.
Parallel Development
Run multiple AI agents on the same repository — locally, in the cloud, or with OpenClaw. SpecWeave's increment files are the coordination layer:
Agent 1 (local Claude Code) Agent 2 (cloud) Agent 3 (OpenClaw)
working on: 0001-auth working on: 0002-payments working on: 0003-notifications
│ │ │
└──────────────────────────────┼───────────────────────────┘
│
.specweave/increments/
├── 0001-auth/tasks.md ← Agent 1's scope
├── 0002-payments/tasks.md ← Agent 2's scope
└── 0003-notifications/tasks.md ← Agent 3's scope
How it works:
- Create increments for each feature:
/sw:increment "auth",/sw:increment "payments" - Each agent picks an increment and runs
/sw:auto— tasks.md tracks exactly what's done - Agents work in isolated scopes — different files, different specs, different tests
- Quality gates (
/sw:grill) ensure consistent standards regardless of which agent built it - Progress syncs to GitHub/JIRA so you see everything in one place
Why this matters: OpenClaw and Claude Code sessions are stateless by default. SpecWeave's spec/plan/tasks files persist across sessions and agents — your coordination layer survives restarts, crashes, and context window limits.
Agent team commands:
| Command | Purpose |
|---|---|
/sw:team-orchestrate "feature" | Split feature across parallel agents |
/sw:team-status | Monitor all agent progress |
/sw:team-merge | Merge completed work in dependency order |
Core Commands
| Command | Purpose |
|---|---|
/sw:increment "feature" | Create spec + plan + tasks |
/sw:auto | Autonomous execution |
/sw:do | Execute one task at a time |
/sw:grill | Code review before close |
/sw:done | Close with quality validation |
/sw:sync-progress | Push to GitHub / JIRA / ADO |
/sw:next | Auto-close + suggest next |
Integrations
| Platform | What Syncs |
|---|---|
| GitHub | Issues, PRs, milestones — bidirectional |
| JIRA | Epics, stories, status |
| Azure DevOps | Work items, area paths |
When you close an increment, external tools update automatically.
How It Compares
| Capability | SpecWeave | BMAD Method | GitHub SpecKit |
|---|---|---|---|
| Parallel agent coordination | Increment-scoped isolation | No | No |
| Autonomous execution | Hours of unattended /sw:auto | No | No |
| Quality gates | Code Grill before every release | No | No |
| Living documentation | Auto-updated after every task | Manual | Manual |
| Self-improving AI | Learns from corrections | No | No |
| External sync | GitHub / JIRA / ADO bidirectional | No | No |
| Specialized skills | 100+ (PM, QA, DevOps, ML...) | 21 agents | None |
| Works with OpenClaw | Yes | Partial | Partial |
| Spec/plan/tasks workflow | Yes | Yes | Yes |
| Agent-agnostic | Claude Code + OpenClaw + Copilot + Codex | Multi-IDE | Multi-IDE |
Built With SpecWeave
This framework builds itself. Every feature, bug fix, and release is spec-driven.
Browse increments — see how SpecWeave develops SpecWeave.
Documentation
spec-weave.com — guides, examples, and full reference.
Community
Discord · YouTube · GitHub Issues