specweave weekly downloads statistics

SpecWeave

Change agents. Keep the thread. Intent-first development: settle what you want before the code, hand the work between Claude, Codex, Grok and any other tool in two words, and close it with evidence.

Install

init writes AGENTS.md (read by Codex, Grok, Cursor, Gemini and Copilot), a two-line CLAUDE.md that imports it, and the skills for Claude Code and Codex. Nothing else runs in the background.

SpecWithCode: the free workspace on top

SpecWithCode is a desktop app built on SpecWeave. Describe the work once and a coordinator splits it across Claude Code, Codex, Grok or Cursor workers on your own machines, with the spec, evidence and handoff in git. It is free for every developer and team: no markup, no token resale, no seat fee to run agents on your own machines. Early access, Apple silicon Macs. Download · Pricing

Keep your repositories where they are

An existing workspace can register nested, sibling or external checkouts without moving files or initializing a second planning root:

--workspace selects planning authority; SPECWEAVE_WORKSPACE carries that context to hooks. Existing IDs and child plans stay intact. Workspace adoption explains previews, identity, permissions and migration limits.

Out of tokens? Say "hand off"

That is the whole handoff. "Hand off" runs specweave handoff: it releases your task claims, records why you stopped, and pushes your branch plus a snapshot of your uncommitted edits. "Pick up" runs specweave pickup in any other tool, account, machine or cloud session (a Claude Code Projects thread, a Codex cloud task): it brings that work into the checkout and prints the next task with its acceptance criteria. Nothing to copy, no paths to paste.

Running out mid-task? specweave auto-handoff on, once per machine, makes it automatic: when a session reaches 90% of your plan's 5-hour or weekly limit, it hands off by itself and tells you to say "pick up" elsewhere. Claude Code reads the limit through its status line (your own status line keeps working) and Codex through a Stop hook. Under the threshold it costs no tokens. --at 85 changes the threshold and off undoes every change.

specweave report writes an HTML timeline of who did what on an increment (tools, sessions, handoffs, pickups, test evidence), straight from the ledger.

The loop

| # | Say or run | What happens |

| 1 | "pick up" · specweave pickup | The open increment, the next task with its acceptance criteria, claims held by others, branch state, notes and project memory, in one read. | | 2 | /sw:increment · specweave create-increment "" | One spec.md: Problem, Scope, Acceptance Criteria, Approach and the Tasks. | | 3 | /sw:do · specweave task claim T-01 → task done T-01 --run "" | Work a task. done refuses a failing test and stores the evidence in the ledger. | | 4 | specweave verify · /sw:review · specweave review | Runs your test, lint and build; a fresh-context review cites path:line, and specweave review hands the diff to another model family. | | 5 | /sw:done · specweave complete | Closes on a green verify. Acceptance criteria are met when their tasks are done; nobody ticks boxes. | | 6 | "hand off" · specweave handoff | Stop anywhere; the next tool picks up. |

An increment is one folder, .specweave/increments/NNNN-slug/, with one file you read (spec.md) and one the CLI appends to (ledger.jsonl). Increments from 2.x with a tasks.md keep working unchanged.

Works the way Claude Code Projects work

| Claude Code Projects | SpecWeave |

| A thread: one session, one branch, one PR | One increment | | The thread's checklist | The ## Tasks of that increment's spec.md, state in ledger.jsonl | | Project memory (MEMORY.md + one file per fact) | .specweave/memory/, same format, committed, so every tool and account sees it | | Threads passing notes | specweave note "" on another increment |

Project memory in claude.ai stays with one account. .specweave/memory/ travels with the code, so Codex, Grok and a second Claude subscription start from the same decisions.

Six core skills, five optional

The CLI is the product and runs in any tool or in CI. The skills expose it to coding agents: /sw: in Claude Code, sw- in .claude/skills/ (for Projects threads, where plugins do not load) and .agents/skills/ (Codex, Grok).

Core, in every project:

| Skill | Use it for |

| increment | Settle your decisions, then plan the work as one spec.md. | | do | Claim a task, implement it, close it with evidence; also unattended, or in parallel lanes. | | auto | The unattended run of do, started by you, until the tasks run out. | | review | Adversarial review by a fresh context or another model family; findings cite path:line. | | done | Verify, review, specweave complete. | | handoff | "Hand off" and "pick up". |

Optional, installed per project when enabled or detected (in Claude Code they are /sw-grill-me and so on):

| Skill | Use it for | Detected by |

| grill-me | An interview in rounds, each question with a recommended answer, recorded under ## Decisions (after Matt Pocock's grilling). | planning.deepInterview: deep | | glossary | GLOSSARY.md: each domain term across business, data, code and UI, with words to avoid. | a GLOSSARY.md or GLOSSARY-MAP.md | | sync | GitHub, Jira and Azure DevOps, only when you run it. | a configured tracker | | project | Shared goals, artifacts and briefs across tools. | .specweave/project/hub.json | | jev | Closed-set decisions in about 250 ms via Jev. | jev.enabled |

brainstorm and team are retired: the Decide step is in increment, the full interview is grill-me, and parallel agents are do's Parallel lanes. specweave update removes SpecWeave's own copies of retired skills.

Upgrade to 3.0…

Description from the npm listing.