Co-Pilot

Updated a month ago

specweave

Name: specweave
Rating: 4.3 (27 reviews)
Author: anton-abyzov

Aanton-abyzov

0.0k

anton-abyzov/specweave

Agent Score

💡 Summary

SpecWeave automates AI-driven coding tasks with permanent documentation and seamless integration.

🎯 Target Audience

Software developers looking for automationProject managers needing documentationTeams using GitHub/JIRA for project managementDevOps engineers wanting CI/CD integrationAI researchers exploring coding tools

🤖 AI Roast: “It's like having a personal assistant that never sleeps, but does need Node.js to function.”

Security AnalysisMedium Risk

The README suggests potential risks such as dependency vulnerabilities and network access for syncing with external tools. To mitigate, ensure regular updates of dependencies and use secure configurations.

SpecWeave

The Enterprise Layer for AI Coding.

Permanent memory, GitHub/JIRA sync, quality gates, autonomous execution. Ship features while you sleep.

npm install -g specweave   # Requires Node.js 20.12.0+

Quick Demo

/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...

Why SpecWeave?

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.

Key Differentiators

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:

## Skill Memories
<!-- Auto-captured by SpecWeave reflect -->
- 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.

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.

Install

Prerequisites

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

node --version   # Check version

Getting SyntaxError: Unexpected token 'with'? Your Node.js is too old. Upgrade instructions →

New Project

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

npm install -g specweave
cd your-project
specweave init .

Then:

/sw:increment "Add dark mode"   # Create spec + plan + tasks
/sw:auto                        # Ship while you sleep

Core Commands

| Command | Purpose | |---------|---------| | /sw:increment "feature" | Create spec + plan + tasks | | /sw:auto | Autonomous execution (hours) | | /sw:do | Execute one task at a time | | /sw:done 0001 | Close with quality validation | | /sw:sync-progress | Push to GitHub/JIRA/ADO | | /sw:next | Auto-close + suggest next |

53 total commands →

External Integrations

| 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.

/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

Works On Everything

| 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 |

CLI Commands

| Command | Purpose | |---------|---------| | specweave init . | Initialize project | | specweave update | Full update: CLI + plugins + instructions |