What is SpecWeave?
SpecWeave is the AI development framework that doesn't lose your work.
Every AI coding tool promises productivity. But after the chat ends, your specs disappear into chat history, your architecture decisions are forgotten, and new team members start from zero.
SpecWeave is the only framework where AI decisions become permanent, searchable documentation.
Stop Repeating Yourself
Every app needs the same things: auth, tests, docs, deployment. Without SpecWeave, you dictate every step:
"Create user authentication"
"Now add tests for that"
"Document the architecture"
"Update JIRA with progress"
"Create the PR description"
With SpecWeave:
/sw:increment "User authentication"
/sw:auto
# Done. Tests, docs, sync - all handled.
One Command = Many Prompts
| What You Used To Dictate | SpecWeave Command |
|---|---|
| "Create spec with user stories..." | /sw:increment "feature" |
| "Implement, test, fix, repeat..." | /sw:auto (runs for hours) |
| "Update GitHub/JIRA..." | /sw:sync-progress |
| "Review for security..." | Auto-activates on keywords |
| "Commit and create PR..." | /sw:save |
Built-In Expertise
SpecWeave isn't just shortcuts - it's encapsulated expertise:
- 15+ AI agents (PM, Architect, QA, Security) work in parallel
- Skills auto-activate - mention "security" and security expertise loads
- Quality gates enforce what senior devs know: tests before merge, docs before close
Real result: 5 production apps built with SpecWeave. Then 10 and 14-year-old daughters learned to do the same - because the expertise is in the framework, not in knowing what to ask.
The Problem: Lost Work
Traditional AI-assisted development:
- Tell AI: "Build me a feature"
- AI generates code
- Test it manually
- Fix bugs as they appear
- (Maybe) document it later
- Repeat for next feature
The result:
- No documentation = regression risk
- No specs = unclear requirements
- Manual testing = inconsistent quality
- Context bloat = expensive AI costs
- No architecture = technical debt
- New team members = 2 weeks onboarding
The Solution: Permanent Knowledge
SpecWeave enforces Spec-Driven Development:
Permanent = survives chat sessions | Auto-sync = updates automatically
Key Principles
- Specification Before Implementation - Define WHAT and WHY before HOW
- Living Documentation - Specs evolve with code, never diverge
- Context Precision - Load only what's needed (70%+ token reduction)
- Test-Validated Features - Every feature proven through automated tests
- Regression Prevention - Document existing code before modification
- Framework Agnostic - Works with ANY tech stack
How It Works
1. One Command Creates Foundation
/sw:increment "User authentication with OAuth"
AI agents (PM, Architect, Planner) create:
.specweave/increments/0001-user-authentication/
├── spec.md <- WHAT: User stories, acceptance criteria
├── plan.md <- HOW: Architecture, ADRs, tech decisions
└── tasks.md <- DO: Tasks with embedded tests
2. One Command Builds
/sw:do
Autonomous execution through all tasks with quality validation.
3. One Command Closes
/sw:done 0001
Three quality gates validate completion:
- All tasks complete
- 60%+ test coverage
- Living docs updated
4. Auto-Sync Everywhere
Your work syncs to GitHub Issues, JIRA, and Azure DevOps automatically.
Who Should Use SpecWeave?
Perfect For
- Enterprise teams building production systems
- Startups needing scalable architecture from day one
- Solo developers building complex applications
- Regulated industries (healthcare - HIPAA, finance - SOC 2)
- Teams migrating brownfield codebases to modern practices
Use Cases
- Greenfield projects: Start with comprehensive specs
- Brownfield projects: Document existing code before modification
- Iterative development: Build documentation gradually
- Compliance-heavy: Maintain audit trails and traceability
Core Features
| Feature | Benefit |
|---|---|
| 15+ AI Agents | PM, Architect, Tech Lead, QA, Security, DevOps work autonomously |
| Living Documentation | Specs auto-update after every task via hooks |
| 70% Token Reduction | Context precision loads only what you need |
| Quality Gates | Three-gate validation before closing increments |
| External Sync | Push specs to GitHub/JIRA/ADO, read status back |
| Brownfield Support | Import existing docs, create retroactive specs |
| Multi-Language | Work in ANY language (Russian, Spanish, Chinese, etc.) |
What You Get vs. Current State
| Before | After SpecWeave |
|---|---|
| Specs in chat history | Permanent, searchable specs |
| Manual JIRA/GitHub updates | Auto-sync on every task |
| Tests? Maybe later... | Tests embedded in tasks (60%+ enforced) |
| Architecture in your head | ADRs captured automatically |
| "Ask John, he knows" | Living docs, always current |
| Onboarding: 2 weeks | Onboarding: 1 day |
Getting Started
npm install -g specweave
cd your-project
specweave init .
Then in Claude Code:
/sw:increment "Your first feature"
/sw:do
/sw:done 0001
Next: Key Features ->