| Connection | Useful when | Start here |
|---|---|---|
| GitHub | Issues and repository work belong together. | GitHub guide ↗ |
| Jira | Product and engineering share an existing delivery process. | Jira setup ↗ |
| Azure DevOps | Your organization plans with work items and boards. | Azure DevOps setup ↗ |
One explicit sync surface.
specweave sync setup specweave sync status specweave sync push <increment-id> specweave sync pull <increment-id>
Configure the target before pushing. A push can update remote issues; it is an external write. Review the configuration and run it at meaningful milestones rather than after every small file edit.
Keep authority clear.
The local specification and ledger record engineering intent and verified task progress. A remote ticket provides planning context and a familiar place for stakeholders. A closed remote issue alone is not proof that local acceptance criteria passed.
The current pull command reports external changes for review. It does not merge those changes into local files. Automatic two-way reconciliation, silent conflict resolution, and universal hierarchy mapping are not promises of this release.
Do I need an integration?
No. The board, specifications, task ledger, and handoffs work locally. Add a tracker only when it makes collaboration easier.
Will changing a card update Jira?
A board state change is local. Use the explicit sync workflow for a linked increment when you want to publish progress to a configured tracker.
How should an enterprise evaluate this?
Start with one repository and a disposable tracker project. Verify mappings, permissions, reopened tickets, partial failures, and retry behavior before expanding. Keep your established tracker as the planning surface.
Why not replace Linear, Jira, or Azure Boards?
SpecWeave focuses on a different boundary: carrying intent and implementation evidence across coding tools. If your tracker and harness already solve that boundary for your team, avoid adding duplicate process.
Go deeper when it helps.
Integration architecture and ownership · CLI reference · The work model