The AI Delivery Standard

How we ship AI-written code a team can trust. The plan is reviewed before code exists, every ticket gets a lane, and a person merges exactly the commit that was checked.

At a glance

Plan
Drafted by an agent, reviewed by a developer and the product owner
Tickets
Linked to the plan, each with a lane
Checks
Automated, agent review, a human for structural work
Merge
A person, for one exact commit

Humans at the plan and at the merge.

Agents draft, build and review everything in between. Each ticket carries its lane, its checks and its proof. Try it: approve the plan, switch a lane, run the reviews, merge.

checkout-v2 / refinementhuman stepagent step
human
PLAN-031, drafted by agent
  • Split validation from the payment step
  • Migrate saved addresses, keep old rows readable
  • Out of scope: new payment providers

Awaiting approval, 1/2

linked to plan
agent

A feature within one area. Plan, automated checks and agent review.

  • Automated checks lint, types, tests: green
  • Agent reviewpass 1/2
human
  • Plan approved by dev and PO (open)
  • Automated checks green (met)
  • Agent review clean, 2/2 (open)

2 requirements open

The ticket is the memory, not the session.

Every ticket gets a lane.

The lane is set in refinement, before anyone starts. It decides how much checking a change needs: routine work moves fast, risky work always meets a person.

Routine

Copy, config, dependencies, small fixes.

  • No plan needed
  • Automated checks
  • No agent review
  • No extra reviewer

Standard

A feature within one area of the product.

  • Reviewed plan
  • Automated checks
  • Agent review with proof
  • No extra reviewer

Structural

API contracts, migrations, auth, payment, customer data.

  • Reviewed plan
  • Automated checks
  • Agent review with proof
  • A human reviewer

Whatever the lane, a person merges, and an approval counts for exactly one commit.

Want this for your team?

hq@22bits.de

Replies within one working day.