Implement

Your agent cuts the approved Plan into slices and builds each one test first. You start the build, and it runs on its own.

An example task in a fictional project.

Start the build

In the App

Approve and build here continues the planning session after its turn. Otherwise Start the build on Plan opens the build card:

AgentThe coding agent for this build, with What's different for that agent.

Build model and EffortFor the session that writes and tests the code, with the recommended model and why.

Subagent modelClaude Code only: the model for slices it hands to subagents.

Files and WorkspaceAttachments, where it runs, and the branch or worktree.

Press Approve & start. Closing the sidebar keeps the run (agent runs).

In my own agent

A planner waiting in your own agent shows Build in <agent> · your agent: run your agent's compact command, then say "build here".

Otherwise the card shows one request box with Copy and a folder chip. Paste the request into any agent, or ask in your own words. For a pending Plan, Approve and copy approves it and copies the request; after approval, Ready to build offers Copy prompt.

Tip

Runs start in the agent's own permission mode. Its own permission and sign-in prompts still need you, and a stop or pause stays in force.

Where the build lands

A new branch or worktree starts at this checkout's HEAD. A worktree's name sets its branch and its folder beside the project; by command, qualitylayer branch new [name]. A pull request needs a branch other than its target. Pushes and deployments need the Plan's authorization; you merge.

While the agent builds

Open full size ↗ Open full size ↗

1. Slices

   Your agent cuts the Plan into slices that each work end to end, thinnest first, and each slice into task cards. For a bug, the reproduction comes before the repair.

2. Test first

   For each card it writes a failing test, builds the change, fixes failures and commits. It may hand independent slices to subagents.

3. Done means

   Test runs are recorded with their commit and exit code, so Verify can cite them. Each Done means step runs on the built tree before Verify starts.

The boardEvery slice of a small build; the one in work of a larger one. A task opens to its card: files, test first, done when.

Under the boardKnown limits, Decided while building and Program design. A decision says whether it is build order or an amendment to what you approved.

Your partA matter only you can settle comes as one question; the build goes on while you answer.

Note

A failing check is your agent's to fix, so the page does not flag it, and the final approval still refuses a red check. A login, secret or other prerequisite only you can provide never counts as passed. If it is still missing at the end of Verify's checks, it reaches you as one question; the App never takes the secret.

When the build is done

The session decides when the build is ready, and Verify starts on what it committed. Unticked cards and open needs stay open in Verify, never passed.