メニュー
Use when running an active autopilot-codex session — explains the plan→implement→review→verdict cycle, state machine, and termination conditions. Required reading when status='running' and the implementer needs to act inside the loop.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | autonomous-loop |
| description | Use when running an active autopilot-codex session — explains the plan→implement→review→verdict cycle, state machine, and termination conditions. Required reading when status='running' and the implementer needs to act inside the loop. |
| when_to_use | status=running and you need to know how the loop drives | unsure what verdict 'continue' means | mapping decision values to state transitions |
| allowed-tools | Bash(autopilot-codex:*), Read, Edit, Write, MultiEdit, Glob, Grep |
You are the implementer. Codex (the manager) plans, reviews each diff, and decides at the end of every turn whether the goal is achieved. Your job is to keep the loop honest: implement one task at a time, commit when green, never invent scope.
┌──────────────────────────────────┐
│ idle │
└──────────────────────────────────┘
│ codex-plan
▼
┌──────────────────────────────────┐
┌───▶│ running │───┐
│ └──────────────────────────────────┘ │
│ │ │ │ │ │ │
│ Edit │ │ Stop │ │ │ │
▼ │ ▼ │ ▼ ▼ │
review │ verdict │ budget iter │
(fix?) │ (continue?) │ (over?) cap? │
│ │ │ │ │ │ │
│ │ │ │ │ │ │
└──────┘ │ │ ▼ ▼ │
▼ ▼ stopped_ stopped_
done aborted budget iteration_
limit
State lives at ${CLAUDE_PLUGIN_DATA}/state.json. current_task is the
ONE task you should be implementing right now. base_sha is what review
diffs against. iteration is incremented per verdict call.
current_task from state — its id, title, files, steps,
acceptance, tests. The acceptance array is your contract; review
judges by it.tests listed, write the failing test first (RED),
then implement (GREEN), then refactor.<type>(<scope>): <task title> ≤ 72 chars.bridge verdict and either advance
you to the next task or terminate the loop.decision: "approve" → green light; move to next task on next Edit.decision: "fix" → PostToolUse hook returns decision:"block" with
the issue list. Do not advance. Address the issues; the next Edit
re-fires review.decision: "reject" → revert the change (git restore -SW <files> or
git reset depending on staging) and consult codex-manager for a
re-plan. Do not try a different fix on top of a rejected change.decision: "continue" from verdict → Stop hook returns
decision:"block" with the next task contract baked in. Implement it.decision: "done" from verdict → loop terminates; status='done'.decision: "abort" from verdict → status='aborted'; user takes over.The Stop hook lets Stop proceed (no block) when any of:
status == "done" — Codex says goal achieved.status == "aborted" — Codex aborted (or no_progress_streak ≥ 3
consecutive 'continue' verdicts without commits).status == "stopped_iteration_limit" — iteration >= max_iterations
(default 30).status == "stopped_budget" — budget_used_usd >= budget_usd (default
$5.00). See safety-rails skill.codex CLI missing or codex login broken — Stop hook logs and lets
the user finish manually./autopilot-codex:codex-plan <revised goal>. Don't
paper over with a different fix on top.safety-rails, side-effecting operations (git push, npm publish,
terraform apply) need explicit user approval./autopilot-codex:codex-status — full state JSON./autopilot-codex:codex-next — just the current task contract./autopilot-codex:codex-stop [reason] — disable the loop; hooks
become no-ops on the next turn.Use when interpreting state mutations during plan/review/verdict transitions — explains exactly which fields the bridge writes when, so the implementer can debug 'why is current_task suddenly T3' or 'why is base_sha old'.
Use when deciding whether a question warrants spawning a Codex turn or you can answer locally — covers the cost/value matrix and which subagent or command is the right entry point for each kind of consultation.
Use whenever you're about to run a destructive Bash command, push code, or spend Codex tokens — explains every cap and denylist this plugin enforces and how to extend them.
Use whenever the user invokes /autopilot-codex:* in this repo, OR mentions "autopilot", "Codex manager", "Codex architect", or asks Codex to plan/review for them. Establishes the role split — OpenAI Codex is manager/architect, Claude Code is implementer — and the operating contract.