Every coding agent reads it.
SpecWeave needs no service and no account. Coding agents read the files in your repository, so Claude Code, Codex, Grok and the rest pick up the same spec and ledger.
Coding agents
The CLI is the same in every tool, so a tool without skills still runs the loop. Switching between them, or between two subscriptions of one, is a handoff and a pickup. More in Codex, Grok and others.
Claude Code, including Projects threads
- Reads
- CLAUDE.md, which imports AGENTS.md
- Skills
.claude/skills/
Codex
- Reads
- AGENTS.md
- Skills
.agents/skills/
Grok Build
- Reads
- AGENTS.md and CLAUDE.md
- Skills
.grok/skills/, .agents/skills/, Claude Code skills
Cursor, GitHub Copilot, Gemini CLI, OpenCode
- Reads
- AGENTS.md
- Skills
Their own folders, or the CLI directly
Issue trackers (optional)
A push is an external write, so it happens only when you run it. Starting, pausing or resuming an increment never touches a tracker, and nothing creates issues except a push. Completing an increment closes the issue a push linked only when the close-on-complete setting is on; sync setup turns it on, and you can turn it off. sync pull reports what changed in the tracker for you to review; it does not rewrite your local files.
GitHub Issues
Useful whenIssues and code live in the same place.
GitHubJira
Useful whenProduct and engineering share an existing delivery process.
Jira and Azure DevOpsAzure DevOps
Useful whenYour organization plans with work items and boards.
Jira and Azure DevOps
specweave sync setup # connect a tracker specweave sync status # credentials, health, what would change specweave sync push 0042 # publish progress, when you choose specweave sync pull # report changes made in the tracker
Who owns what
A closed issue is not proof that acceptance criteria passed; a passing verify report is.
The spec and the ledger
The spec and the ledger record what done means and what was verified.
Planning context
The tracker holds planning context: priority, assignee, labels and the place stakeholders look.
Do I need a tracker?
No. Specs, the ledger, handoffs and the dashboard all work locally. Add a tracker when it makes collaboration easier.
Will moving a card on the dashboard update Jira?
No. Board changes are local. Run specweave sync push for the increment when you want the tracker updated.
How should a team evaluate this?
Start with one repository and a throwaway tracker project. Check the mapping, permissions, reopened issues and partial failures with sync push --dry-run before connecting the real one.