payments

```bash

/sw:increment "User authentication"

/sw:auto # Ship while you sleep

```

What happens:

• AI creates spec + plan + tasks
• Executes autonomously for hours
• Tests, fixes failures, syncs to GitHub/JIRA
• You review finished work

```

[08:23:41] [Planning] Analyzing T-003: Implement refresh token rotation

[08:24:12] [Implementing] Writing src/auth/token-manager.ts

[08:25:33] [Testing] Running tests... FAILED

[08:25:47] [Fixing] Adjusting implementation...

[08:26:15] [Testing] Re-running... PASSED

[08:26:22] [Done] T-003 complete. Moving to T-004...

```

---

Every AI coding tool loses context when the chat ends. SpecWeave creates permanent documentation:

```

.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

```

After 6 months: Search "OAuth" → find exact decisions, who approved, why it was built that way.

---

Lazy Plugin Loading (99% Token Savings)

SpecWeave loads plugins on-demand based on your prompt keywords:

| Scenario | Without Lazy Loading | With Lazy Loading |

|----------|---------------------|-------------------|

| Non-SpecWeave work | ~60k tokens | ~500 tokens |

| SpecWeave work | ~60k tokens | ~60k (when needed) |

Say "React frontend" → frontend plugin loads. Say "Kubernetes deploy" → k8s plugin loads. No manual configuration.

Self-Improving Skills

SpecWeave learns from corrections. When you fix something, it captures the learning:

```markdown

• Always use vi.hoisted() for ESM mocking in Vitest 4.x+
• Prefer native fs over fs-extra in new code

```

Next time, it won't make the same mistake.

Structured Documentation (No Root Bloat)

Everything stays organized in .specweave/:

```

.specweave/

├── increments/####-name/ # Feature specs + tasks

├── docs/internal/ # Living documentation

│ ├── architecture/adr/ # Architecture Decision Records

│ └── specs/ # Feature specifications

└── config.json # Project configuration

```

Your project root stays clean. No scattered markdown files.

Deep Interview Mode (NEW)

For complex features, enable Deep Interview Mode during init. Claude asks 40+ questions about architecture, integrations, UI/UX, and tradeoffs before creating specifications:

```

Deep Interview Mode

For big features, Claude can ask 40+ questions about architecture,

integrations, UI/UX, and tradeoffs before creating specifications.

Enable Deep Interview Mode? [y/N]

```

Inspired by [Thariq's workflow](https://x.com/trq212/status/2005315275026260309) (Claude Code creator): "For big features Claude might ask me 40+ questions and I end up with a much more detailed spec."

15+ AI Agents Working Together

| Agent | Role |

|-------|------|

| PM | Requirements, user stories, acceptance criteria |

| Architect | System design, ADRs, tech decisions |

| QA Lead | Test strategy, quality gates |

| Security | OWASP review, vulnerability scanning |

| DevOps | CI/CD, infrastructure, deployment |

Agents auto-activate based on context. Mention "security" → security expertise loads.

LSP Integration (100x Faster Code Understanding)

SpecWeave leverages Language Server Protocol for semantic code intelligence:

| Operation | Without LSP | With LSP |

|-----------|-------------|----------|

| Find all references | Grep + read 15 files (~10K tokens) | Semantic query (~500 tokens) |

| Check type errors | Build + parse output (~5K tokens) | getDiagnostics (~1K tokens) |

| Navigate to definition | Grep + verify (~8K tokens) | goToDefinition (~200 tokens) |

LSP plugins work automatically when editing code. Edit a .cs file → csharp-lsp activates. Edit .ts → typescript-lsp activates. No configuration needed.

```bash

# Install language servers for your stack

npm install -g typescript-language-server typescript # TypeScript

pip install pyright # Python

dotnet tool install -g csharp-ls # C#

```

[Full LSP Guide →](https://spec-weave.com/docs/guides/lsp-integration)

---

Prerequisites

Node.js 20.12.0+ required (recommend Node.js 22 LTS).

```bash

node --version # Check version

```

> Getting SyntaxError: Unexpected token 'with'? Your Node.js is too old. [Upgrade instructions →](https://spec-weave.com/docs/guides/troubleshooting/common-errors#node-version-error)

New Project

```bash

npm install -g specweave

mkdir my-app && cd my-app

specweave init .

```

Then describe what you want in Claude Code:

```

"Build a calculator app with React"

```

Existing Project

```bash

npm install -g specweave

cd your-project

specweave init .

```

Then:

```bash

/sw:increment "Add dark mode" # Create spec + plan + tasks

/sw:auto # Ship while you sleep

/sw:grill 0001 # Code review before close

/sw:done 0001 # Complete with validation

```

---

| Command | Purpose |

|---------|---------|

| /sw:increment "feature" | Create spec + plan + tasks |

| /sw:auto | Autonomous execution (hours) |

| /sw:do | Execute one task at a time |

| /sw:grill 0001 | Code review before close |

| /sw:done 0001 | Close with quality validation |

| /sw:sync-progress | Push to GitHub/JIRA/ADO |

| /sw:next | Auto-close + suggest next |

[53 total commands →](https://spec-weave.com/docs/commands/overview)

---

| Platform | Capabilities |

|----------|--------------|

| GitHub | Issues, PRs, milestones, bidirectional sync |

| JIRA | Epics, stories, status sync |

| Azure DevOps | Work items, area paths |

Automatic sync: When you close an increment (/sw:done), external tools update immediately. Task progress syncs at session end.

```bash

/sw:sync-progress # Manual: Push updates to ALL tools

/sw-github:sync 0001 # Manual: Sync specific increment to GitHub

/sw-jira:sync 0001 # Manual: Sync specific increment to JIRA

```

---

| Scenario | What Happens |

|----------|-------------|

| 10-year legacy codebase | Brownfield analysis detects doc gaps |

| Weekend MVP | Full spec-driven development |

| 50-team enterprise | Multi-project sync to JIRA/ADO |

---

| Command | Purpose |

|---------|---------|

| specweave init . | Initialize project |

| specweave update | Full update: CLI + plugins + instructions |

Troubleshooting

Run specweave update - this fixes 98% of issues (updates CLI, plugins, and instructions).

---

• Node.js 20.12.0+ (recommend 22 LTS)
• Any AI coding tool (Claude Code recommended)
• Git repository

---

> This framework builds itself. Every feature, bug fix, and releas