Build software step by step with the Dev Pipeline

The Dev Pipeline is for people who build software with agents. Type /dev-pipeline and a task, and the agent works through it in order: plan, red team (a hard look for flaws), build with tests, polish, docs, and a final check. It works on its own copy of the code and stops at a branch marked ready to merge; it never pushes or merges by itself.

Turn it on#

Preview means the panel is still in development and is off until you turn it on.

1. 1

   In Settings > Optional Features, turn on Enable Dev Pipeline skill (the card below). This adds the /dev-pipeline command to Claude Code and also shows a Dev Pipeline row under Developer Tools.

2. 2

   Open the panel's Setup tab and, under Which repositories, switch on the projects to use it in.

3. 3

   In a session in one of those projects, type /dev-pipeline and your task.

The Dev Pipeline switch above, in Lab, is optional: it shows the panel even while the skill is off.

Choose where it stops for you#

After each of the first five steps the run reaches a gate: a point where you approve, give feedback or stop. In the panel's Setup tab, Gate auto-approval has a switch for each gate (Plan, Red Team, Build, Elegance, Docs) and Auto-approve every gate. At first the plan gate waits for you and the other four approve themselves when their step reports done.

A gate that asks you a question is never approved for you, whatever the switches say.

Watch your runs#

The Live tab lists every running pipeline by project: the step it is on, a count of runs waiting for you (with Approve), and its spend so far. If a session dies partway, its run is kept and the panel offers Adopt, which starts a new session that picks it up where it stopped. Adopting starts a paid session, only when you click it.

Keep agents off your main branch#

Git guardrails protect every agent Yardmaster runs, not just pipeline runs. With them on (they are on at first), an agent can't commit or push to a protected branch such as main, edit files while a project sits on one, or throw away work with git stash.

Change them in the Setup tab or Settings > Optional Features: switch them to warn only, edit the protected branches, leave out a project, or pause them for a few minutes. Pausing them and leaving out a project are yours alone: agents and your phone can't do either.

They also protect Codex sessions that Yardmaster starts, and an inbox notice tells you if Codex ever stops running the guardrail. Codex works in the project folder itself, so on a project sitting on main or master it can't edit files or commit until it makes its own worktree (it is allowed to). Codex sessions billed through OpenRouter are not covered yet. They protect Antigravity sessions too, checked live in Antigravity 1.4.11.

For Antigravity, Yardmaster adds a small plugin to Antigravity's own folder (~/.gemini/config/plugins/yardmaster-git-guardrails). It runs no check in sessions you start yourself, though Antigravity may ask your permission for a step while it is installed. To remove it, run agy plugin disable yardmaster-git-guardrails in a terminal, or turn Git guardrails off and Yardmaster takes the plugin out at its next start or Antigravity session. If you delete the folder while they are on, Yardmaster puts it back.