# Plan review

Show what the agent is about to do as steps a person can trim, question and accept before anything runs.

For: The person who asked for the work, and sometimes a second reviewer.

Web page: https://candor.themethodic.com/screens/plan-review

## Layouts

### Inline card in the thread

Pick it when: Short plans in a conversation: a handful of steps the person can read at a glance.

Layout: A thread with a plan card of three steps on a rail and Ask for changes and Accept buttons.

Items:

- **Plan** (`plan`, Pro; https://candor.themethodic.com/docs/plan.md): Steps to trim and accept, then the live run; sent back, it shows what was proposed, marked as not accepted.
- **Clarifying questions** (`clarifying-questions`, Pro; https://candor.themethodic.com/docs/clarifying-questions.md): What the agent needs to know first; the recommended answer is marked, never pre-selected.
- **Step list** (`step-list`, free; https://candor.themethodic.com/docs/step-list.md): Ordered steps on a rail that fills as they finish.
- **Comment thread** (`comment-thread`, Pro; https://candor.themethodic.com/docs/comment-thread.md): A question about one step, between people and the agent, anchored to it; it says when the step has changed since, as your app reports it.

```bash
npx candor-ui add plan clarifying-questions step-list comment-thread
```

### Plan beside the evidence

Pick it when: Plans that change real things: reviewers need each step's log, diff and reach next to it.

Layout: The plan down the left; the selected step's log, diff and blast radius on the right.

Items:

- **Review canvas** (`review-canvas`, Pro; https://candor.themethodic.com/docs/review-canvas.md): The plan on one side; a selected step's log, diff, blast radius and reasoning on the other.
- **Blast radius** (`blast-radius`, Pro; https://candor.themethodic.com/docs/blast-radius.md): What a step can reach.
- **Change diff** (`change-diff`, Pro; https://candor.themethodic.com/docs/change-diff.md): The change as files, one tab per file.
- **Review ladder** (`review-ladder`, Pro; https://candor.themethodic.com/docs/review-ladder.md): How much is reviewed before agents act: from Advise to Full delegation.

```bash
npx candor-ui add review-canvas blast-radius change-diff review-ladder
```

### Last look before shipping

Pick it when: The plan has run and the change is about to reach production.

Layout: A full page with the change, a checklist of checks and one Ship button.

Items:

- **Ship review** (`ship-review`, Pro; https://candor.themethodic.com/docs/ship-review.md): What ships, each check it must pass, and who signed off.
- **Test results** (`test-results`, Pro; https://candor.themethodic.com/docs/test-results.md): A test run that leads with what failed.
- **Approval request** (`approval-request`, Pro; https://candor.themethodic.com/docs/approval-request.md): A second person approves the exact change, tied to it by a hash.

```bash
npx candor-ui add ship-review test-results approval-request
```

## Rules that matter most here

- **Nothing is pre-selected in a decision** (https://candor.themethodic.com/principles#nothing-preselected): The recommended answer to a clarifying question is marked, not chosen for the person.
- **Approve the exact change** (https://candor.themethodic.com/principles#approve-the-exact-change): Accepting a plan accepts these steps; if the plan changes, the person is asked again.
- **Reasoning is believed, not verified** (https://candor.themethodic.com/principles#reasoning-is-believed): A step's reasoning is shown as the agent's account, not as something Candor checked.

## Patterns that cover part of it

- Agent plan UI: show the plan before it runs: https://candor.themethodic.com/patterns/agent-plan-ui.md
- Comments on agent work: anchor a discussion to a run, plan or diff: https://candor.themethodic.com/patterns/comments-on-agent-work.md

A full-stack block builds this with an agent route and a store: `plan-build-review` (https://candor.themethodic.com/docs/plan-build-review.md). Each block has a `-claude` twin for the Claude Agent SDK.

## Brief for a coding agent

Paste this to the agent that builds the screen.

```text
Build a plan review with Candor UI: before the agent acts, show its plan as steps in a Plan the person can trim and accept.
Ask first with ClarifyingQuestions; mark the recommended answer but never pre-select it.
Proposed, the person drops steps they don't want and accepts or asks for changes; accepted, the same Plan becomes the live run with each step's status; sent back, it shows what was proposed, marked as not accepted.
For plans that change real things use ReviewCanvas: the plan on one side, the selected step's log, diff (ChangeDiff), BlastRadius and reasoning on the other.
Pass steps as plain data (id, title, status); Candor does not run the plan, your server does.
The agent's reasoning is shown as its own account. If a step's reach couldn't be measured, say so instead of showing an empty list.
Link to the agent-plan-ui pattern for the full flow.

Start from the "Inline card in the thread" layout: A thread with a plan card of three steps on a rail and Ask for changes and Accept buttons.
Candor items: plan (https://candor.themethodic.com/docs/plan.md), clarifying-questions (https://candor.themethodic.com/docs/clarifying-questions.md), step-list (https://candor.themethodic.com/docs/step-list.md), comment-thread (https://candor.themethodic.com/docs/comment-thread.md).
Install: npx candor-ui add plan clarifying-questions step-list comment-thread
Read each item's docs before using it and take its props from there; don't guess them. Pro and Premium items need the person's licence key, which they add with `npx candor-ui key <key>`; don't ask for it.
```