A typechecker for your issue tracker.
npx ztrackA checked box has to cite a commit that's actually in git — or the ticket fails.
Point it at Linear, Jira, or GitHub Issues. Only verified state syncs back.
Green on day one with git + a PR host. Ratchet up the rigor when you're ready.
A verification layer in front of your tracker — no migration.
Like gradual typing — independent categories, each with a depth dial keyed to the instrumentation it costs.
Start with git + a PR host. Claims above your level are counted, never silently dropped.
Agents fix-and-retry a typechecker until it passes — turns out that's the right loop.
Block an agent's turn until check is green. Wire it as a CI gate, or drive the full loop over MCP.
Every other tool records what the agent claims, or scores outputs and forgets. Ztrack is the system of record where “done” is verified.
| Records claim | Validates structure | Verifies evidence of done | |
|---|---|---|---|
| Linear / Jira | ✓ | shape only | ✗ |
| Beads | ✓ | — | ✗ |
| spec-kit / OpenSpec | ✓ | ✓ | ✗ |
| Eval / observability | — | — | scores output |
| Ztrack | ✓ | ✓ | ✓ |
Ztrack runs our own autonomous agent fleet in production.
No — it's a verification layer. Only validated state syncs back to the tracker you already use.
No. The default is green with just git + a PR host. Screenshots and video are opt-in higher tiers.
The hard checks are zero-false-positive facts — a SHA that's actually in git, a file that resolves. You can't pass without doing the work.
spec-kit validates the shape of spec prose. Ztrack verifies evidence of completion, deterministically.
It shines with agents (MCP, stop-hook), but the checks work for any team that wants “done” to mean something.
Apache-2.0, local-first, no SaaS dependency.
npx ztracknpx ztrack