Documentation
Coding Planner
From a coding request to planned, reviewed and delivered work: the full documentation of the AR Labs coding pipeline for AI coding agents.
Choose a guide
01 · Skill
What does it do?
When to use Coding Planner, how it routes work, and what each command produces.
02 · Harness
How does it run?
State, checks, approvals, execution, recovery and delivery, opening with an overview map of the pipeline.
03 · Status
What remains?
Shipped capabilities, current limitations and deferred work.
The system reference
The system reference is the authoritative description of how the pipeline works, written for someone who has not read the code. Every term is defined where it first appears.
| Part | What it covers |
|---|---|
| 1 · The concepts | Campaigns, containers and leaves; the two entry doors; the three routes; commands, floors and gates; refuse against escalate; worktrees; wave and deep modes. |
| 2 · The leaf route | Spec, implementation, independent review (Gate B) and delivery (Gate C). |
| 3 · Containers | The fan-out, waiting on children, integration, and the coverage ledger that carries each promised scenario to a test. |
| 4 · The driver and its hosts | The stateless driver, what it refuses to do, the one-fix review loop, claims, the interactive and headless hosts, and the autonomy dial. |
| 5 · Doctrine | The single writer; guards, floors and gates; channel discipline; revision-bound approvals; evidence; supersession; state and log. |
| 6 · What is not built | What the system does not yet do, stated plainly. |
| Configuration | Every setting the planner reads, with its home, scope, writer, default and reader. |
Reference and background
- The pipeline map: every step and every file of the pipeline, region by region, with a zoomable whole-map chart.
- The entry boundary: the handoff from the clarification interview into planning, where a fresh session resumes from recorded state.
- Agent reference: one screen of routes, steps, floors, verbs and reserved metadata, written for an agent operating the pipeline.
- The two incidents: the planning failures that started the rebuild, as a blameless record of cause and fix.
Who does what?
| Role | Responsibility |
|---|---|
| The skill | Chooses the planning route and delegates to the appropriate command. |
| The harness | Records progress, checks evidence, and runs the next eligible step. |
| The person | Sets direction, resolves decisions, and approves work at the configured checkpoints. |
The core harness is implemented. Some entry, approval and completion gaps remain; what is not built names them.
Elsewhere on the site
The Coding Planner project page gives the overview and history, the coding pipeline describes the method step by step, and the Coding Planner skill page covers the routing skill at its entrance.