What a pilot looks like
| When | What happens |
|---|---|
| Day 1 | A call to pick the repository and the work in flight. We read your current CLAUDE.md, AGENTS.md and prompts. |
| Days 2 to 5 | SpecWeave goes in on a branch you review: one AGENTS.md every tool reads, specs for the work in flight, auto-handoff on for each engineer's tools. |
| Days 6 to 9 | Shared prompts become skills in a private repository, installed with one command into Claude Code and Codex. |
| Day 10 | The drill: an engineer runs out of Claude Code mid-task and Codex picks it up from the handoff. You get the HTML evidence report. |
Questions teams ask
Do we need the pilot to use SpecWeave?
No. npm install -g specweave and the quick start are enough for one developer. The pilot is for teams that want it set up across several people and tools at once.
What triggers a handoff automatically?
specweave auto-handoff on hands off when a usage window passes 90 percent, or a threshold you pick. The next tool runs specweave pickup. Details in handoff and pickup.
Where does our code go?
Nowhere new. Specs, the ledger and handoffs are files in your repository. Private skills live in your own GitHub repositories; Verified Skill syncs and scans them for install.
How do we pay?
Verified Skill plans are paid by card on verified-skill.com. The pilot is invoiced once you have picked a start date.