jkz

Human-in-the-loop multi-agent engineering. You stay the final arbiter.

Most agent tools optimize for autonomy. jkz optimizes for control. Code work runs through three phases (plan, build, QA) across twelve specialized roles. In each, Opus drafts, an adversarial backend tries to break the work, and a validator confirms. Git is the only source of truth; agents never talk to each other directly. Nothing reaches main without you: the system iterates up to three times on its own, but every merge is a human checkpoint.

Get started

New here? The path from zero to your first merged pull request.

Quickstart — your first pipeline, end to end.
Why jkz? — the problem it solves and the constraints behind it.
How jkz works — phases, roles, and the deliberation loop.

Build

The day-to-day, once you know the shape of a pipeline.

Run a pipeline — drive a feature from issue to approval.
Fix a bug — the lighter path for small, scoped changes.
Ad-hoc work — quick edits outside the full pipeline.

Reference

The mechanics, for LLMs and engineers who want the full picture.

Architecture — phase boundaries, roles, model routing.
API reference — auto-generated module exports and signatures.
Design decisions — the ADRs and trade-offs.