Gated implementation
Implementation starts only after a spec is approved and split into build-ordered tasks — and ends at a proposal a human decides on, never a commit the agent makes itself.
How it works
An approved requirements artifact is split into build-ordered tasks, so the coding agent always works from a scoped, human-approved unit of work.
The coding agent writes the change in a sandboxed clone — never against your canonical repo directly — with heavier work routed to a stronger model by an automatic risk-and-complexity read of the task.
What the agent changed, and what it claims it changed, are captured independently and compared — disagreement blocks the proposal and flags it.
Tests, an AC-coverage review, and (for risky diffs) a security pass all attach to the same proposal before anyone looks at it.
Approve, request changes, or reject — the proposal only reaches your canonical repo on an explicit human decision.
The agents behind it
Human control
Proposal gate — cross-checked automatically; approval, request-changes, and reject are the only ways a diff moves.