Intent
The outcome you asked for, in plain language. A useful title, a short explanation, and a place on the board.
What are we trying to change? Open source · Local first · Yours to keep
Change agents.
Keep the thread.
Your tools will change. The work should stay clear. Keep intent, specifications, and verified progress together—across every coding session.
npm install -g specweave
01 / CONTINUITYDifferent tools. One durable record.
Bring your own workflowCodexClaude CodeCursorOpenCodeYour local toolsCLI + files, across harnesses ↗
01 / See the workWhat matters,
What matters,
at a glance.
Start with the outcome. See what is moving, what is waiting, and what is actually verified. Open an intent to find its specification and the work behind it.
Product workspace / Work
Illustrative workspace4 intents1 in progress1 ready for reviewLocal files · no model calls
Backlog1
In progress1
Review1
Done1
Inside this intentKeep checkout resumable
The next agent gets the same acceptance criteria, completed task evidence, and next action.
Explore the work modelExample data above. Your dashboard reads your project. Open it with specweave dashboard.
02 / Go one layer deeperEnough structure.
Enough structure.
Only when needed.
A small fix can stay small. Work that spans agents needs a shared definition of done.
Specification
Attach an increment when scope needs to be explicit. Acceptance criteria and tasks give every agent the same target.
What will count as done?Evidence
Task claims, completion records, checks, and handoffs. Open the record when a green status needs an explanation.
What proves the work is ready?03 / Continue with confidenceA session ends.
A session ends.
The context stays.
Switch because you hit a limit, need a different tool, or want a second opinion. A portable handoff records the next action, decisions, and unfinished work.
Read the handoff guide ↗01
Start in Claude Code
Agree on the outcome. Claim the next task.
02
Keep the evidence
Record completed work and write a handoff.
specweave handoff03
Harness, model, effort, and provider are different dimensions. Keep them distinct when comparing runs.Continue in Codex
Read the same spec. Pick up the next task.
04 / Fit your teamYour tracker.
Your tracker.
Your choice.
Keep GitHub, Jira, or Azure DevOps where your team already plans. Connect delivery progress when it helps. The local workflow stands on its own.
Explore optional integrations ↗05 / In practice
Built with SpecWeave.
Products where we use the workflow to plan changes, track delivery, and carry work between sessions.
Sports platforms
More projects and how we use SpecWeave ↗EasyChamp
League and club tools. SpecWeave supports ongoing work on an established platform.
Career toolsJobWeave
Job search, tailored resumes, recruiter context, and interview preparation.
Developer toolsVerified Skills
Skill discovery, source inspection, and local evaluations with Skill Studio.
The companion project
Explore Verified Skills ↗Better skills. Less baggage.
Find focused expertise, inspect its source, and evaluate whether it helps your workflow.