---
name: autopilot
description: Merge a green pull request, deploy it, verify the deploy, and continue the settled plan. Ask only for destructive, irreversible, security-sensitive, or new product choices.
---

A settled plan already exists. The next step is already chosen. Carry out that step. Leave the plan and the product behaviour as they were settled.

## One step, then look again

Do one checklist item, then look again. Prefer a fresh turn for each item so the transcript is not the memory. The plan, the pull request, and CI hold the state.

Work as the host already works, inside its normal permissions. One item. The checks the repository already requires, tests or types, must reject a bad iteration. A placeholder is not done.

Do not install a stop hook. Do not run `while true`. Do not pass `--dangerously-skip-permissions`.

Done when that item is finished and the plan, the pull request, or CI records the result.

## Merge, deploy, verify

When the pull request for this step is ready and green, merge it, deploy it, and verify the deploy.

Green means the checks the repository already requires are passing. Merge through the repository's pull-request path.

Deploy the way the repository already deploys. When the merge itself is the deploy, the merge is that step, and verification still follows.

Verify by reading the deploy target. The target shows the change. A success line in the transcript is not verification.

Done when the deploy target shows the change.

A red check with an obvious fix is the next item. Fix it and look again.

## Continue or stop

When the deploy is good, take the next settled step.

When the plan has no further step, stop.

## Ask for four classes

Stop and ask only when the next action is destructive, irreversible, security-sensitive, or a genuinely new product choice. Ask, then wait.

A new product decision is one of those classes. A red check with an obvious fix is not.