01
Shape
Turn a raw request into a backlog item with boundaries, acceptance criteria, and a reason to exist.
verifiable agent delivery, from idea to learning
Builder Kit is the agent-delivery kit on top of the Flow Agents engine. It gives the agent a required path: shape the work, probe the repo, plan the change, build it, review it, verify it, publish with evidence, and learn from what reviewers correct. The engine underneath supplies FlowDefinition interpretation, gates, adapters, sidecars, and Trust Bundle evidence. Builder supplies the delivery job.
$ flow-agents kit activate builder
$ Use deliver for issue #214.
✓ pull-work
✓ pickup-probe
✓ plan-work
✓ execute-plan
✓ review-work
BLOCK verify-work: rendered evidence missing
next action: capture browser evidence, then resume
state: .kontourai/flow-agents/builder.build/
Delivery path
Turn a raw request into a backlog item with boundaries, acceptance criteria, and a reason to exist.
Plan the work, execute scoped waves, and route findings back instead of hiding them in a summary.
Move from local evidence to PR, CI, release readiness, and explicit hold or merge decisions.
Capture corrections and repeated misses so the next run starts sharper than the last one.
What Builder sells
Builder is not a new coding agent. It is the delivery discipline around the one you already use. The kit tells the engine which flow to run, what evidence each gate expects, where findings route back, and when a human decision is required.
That makes "done" a verifiable state: not a vibe, not a summary, not a memory artifact from the last context window.
builder.shape
raw idea -> clarified backlog -> executable issue
builder.build
selected work -> plan -> implementation -> evidence
PASS scoped implementation
PASS review finding resolved
PASS CI rerun matched git ground truth
Trust Bundle: claims, evidence, gaps, exceptions
What keeps delivery honest
Builder separates shaping, probing, and planning from implementation so the agent has a route, not just a prompt.
Critique happens before the proof pass, so obvious bugs and architecture misses route back early.
Tests, browser checks, source inspection, CI state, and known gaps become durable artifacts under the Flow Agents engine.
Builder Kit is one first-party kit. Flow Agents remains the neutral engine underneath it, and other kits can run beside Builder without inheriting Builder's delivery assumptions.