---
{
  "n": 17,
  "title": "Reviewing a ticket's plan",
  "abstract": "",
  "refs": [],
  "seen": [
    "system",
    "agent"
  ],
  "data": {
    "starts_on": "ticket.plan_waits",
    "system": true,
    "environment": "main",
    "files": {},
    "started_by": "",
    "only_when_idle": false,
    "talks_in": "",
    "lasting": false,
    "unless": {},
    "dispatch": ""
  },
  "created": 1790359026.284349,
  "updated": 1790367500.115341,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "sequence"
}
---
A ticket's plan waits for your approval. Review it against the ticket before you approve anything.

## Read the ticket and its plan
journal ticket show <ticket n> names its environment, its plan and the board it is on. Read the ticket's card and the plan with journal --env <its environment> plan read <its plan>. If the board's plan_reviewer is a subagent, dispatch the plan-reviewer agent type for this and the next step.

## Check it does the ticket and nothing more
Every phase and to-do serves the ticket's card, none does work the card does not ask for, and it ends with the card's done-when true.

## Approve it or send it back
Approve it with journal ticket approve_plan <ticket n>, or send it back with what must change and why: journal ticket send_back <ticket n> "<the change>". A ticket sent back twice is escalated to the user by itself.