菜单
Use when an ap2 daemon hit trouble — a task failed / froze / retry-exhausted, the daemon restarted with an Active task, a pipeline or agent crashed, the watchdog went quiet, or you need to intervene (`ap2 unfreeze` / `ap2 delete`) or answer 'why did TB-N fail / what just happened?'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when operating an ap2 board — running an `ap2 <verb>` operator-CLI command (start/stop/status/add/approve/unfreeze/rollback/cron/sandbox/…), or reaching for an `autopilot` custom MCP tool (`report_result`, `board_edit`, `operator_queue_append`, `cron_propose`, …) from an agent toolset.
Use when configuring an ap2 daemon — discovering or tuning an `AP2_*` environment knob, authoring `.cc-autopilot/config.toml` keys (`[core]` / `[components.*]` / `[agent_backends]`), or setting up the Codex agent backend.
Use when authoring or revising an ap2 project's `goal.md` (Mission / Done-when / Current focus / Non-goals / Constraints, the delete-test, and the TB-161/TB-164/TB-235 queue-time validators) or running the retrospective `ap2 audit` review of what shipped after a walk-away window.
Use when inspecting ap2 event types, the events.jsonl timeline, prose-judge verification diagnostics, `ap2 logs` / stats-dashboard output, or the `ap2 status` components block (which subsystems are wired and their on/off state).
Check status + recent work of an ap2 daemon for a specific project (board state, daemon liveness, recent events, recent commits, last task summary).
Add a task to an ap2 sandbox project's Backlog by authoring a briefing markdown file and passing it to `ap2 add --briefing-file` (locks TASKS.md, issues a fresh TB-N, no ID collisions). Auto-detects whether to run as the sandbox user directly or escalate via sudo from the main user. Also the operator-facing reference for the task-agent contract, authoring `## Verification` bullets (the `Prose:` prefix + the four shell-bullet pitfalls), and `ap2 classify` impact verdicts — mirroring the daemon-canonical authoring rules in `ap2/ideation.default.md`.
| name | ap2-failure-recovery |
| description | Use when an ap2 daemon hit trouble — a task failed / froze / retry-exhausted, the daemon restarted with an Active task, a pipeline or agent crashed, the watchdog went quiet, or you need to intervene (`ap2 unfreeze` / `ap2 delete`) or answer 'why did TB-N fail / what just happened?'. |
The recovery / escalation manual for an ap2 daemon: what the daemon heals on its own, and where the operator looks (and which verb the operator runs) when something has gone wrong. An operator should never have to hunt through the ap2 source to learn how a crash is salvaged or how to triage a Frozen task. Two self-contained surfaces:
ap2 web
UI for scanning visually.For the CLI verbs named below (ap2 unfreeze, ap2 delete, ap2 check,
ap2 web, ap2 audit) see the ap2-board-ops skill for the full
verb table; for the event types named below (task_implicit_commit,
board_malformed_line, task_unfrozen, task_deleted) and how to tail
them, see the ap2-observability skill.
task_error / cron_error /
ideation_error events carry stderr_tail + prompt_dump paths._infer_result_from_head reads
git log -1; subject starting <TASK_ID>: → synthesize a complete
result. Emits task_implicit_commit._recover_orphans moves it back
to Ready with retry counter incremented.ap2 unfreeze TB-N (resets retry counter atomically),
or permanently removes it with ap2 delete TB-N (atomic; emits
task_deleted event; refuses Active/Ready without --force).DiagnoseReport (board,
recent failures, cron staleness, board health) and posts to
AP2_MM_CHANNELS[0].Board.next_dispatchable skips Backlog tasks
whose (blocked on: TB-X) blockers are unsatisfied. Diagnose
surfaces unsatisfiable cases (Backlog blocked on Frozen).Board._parse flags any line not matching
TASK_LINE_RE; daemon emits dedup'd board_malformed_line event.When you're asked questions about the daemon's state or behavior, here's where to look:
| Question | Read |
|---|---|
| Daemon running? | cat .cc-autopilot/daemon.pid && ps -p <pid> |
| What's the board look like? | awk over TASKS.md for section counts |
| What just happened? | tail -30 .cc-autopilot/events.jsonl | jq -c |
| Why did TB-N fail? | Filter events.jsonl for task=TB-N then read its briefing |
| What did the agent commit? | git log --grep=TB-N --oneline |
| Is a pipeline still running? | ps -p <pid> for the pid in the pipeline_start event |
| What were the verifier's bullets? | The briefing's ## Verification section |
| What did ideation propose? | Last ideation_complete event's summary field |
| What's the latest assessment? | cat .cc-autopilot/ideation_state.md |
| What's been published as "learned"? | cat .cc-autopilot/insights/_index.md |
| What has the operator decided / acked? | cat .cc-autopilot/operator_log.md |
| Recent commits? | git log --oneline -20 |
| Are state files well-formed? | ap2 check (errors: TASKS.md shape, JSON state, cron schema; warnings: stale brief links, insights front matter, missing goal.md) |
The ap2 web command starts a read-only HTTP UI at 127.0.0.1:7820
with /events, /tasks, /task/<TB-N>, /pipelines, /insights,
/ideation_state, /commits, /stats pages. Useful when you want
to scan visually rather than ask the session to summarize.