菜单
Use when running the full plan → review → execute pipeline — write the plan, review it, then implement it behind review and verify gates. The top-level entrypoint that orchestrates writing-plans, plan review, and executing-plans end to end.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | planning |
| description | Use when running the full plan → review → execute pipeline — write the plan, review it, then implement it behind review and verify gates. The top-level entrypoint that orchestrates writing-plans, plan review, and executing-plans end to end. |
| use_when | Driving a body of work from a spec through to merged implementation. |
Load and follow the bundled running-runbooks skill before starting the
runbook.
Stage 1 does not provide Codex hook parity for delegated child dispatch. If this workflow reaches a delegated step that requires automatic child-agent orchestration, stop and report that Stage 2 delegation hook support is required.
Then start the runbook with exactly this command, no added flags:
rundown run rundown:planning
Capture the run id from that command: rundown run prints it at start and every
event carries it as runbookId. This pipeline delegates (step 1), so every
orchestrator command you issue — collect, pass, goto — must carry
--run <rd_…>.
JSON is the agent-facing default; --text is for humans/debugging only — do not
add it here.
Take a body of work from idea to implementation through three gated stages:
write the plan, review the plan, then execute the plan. This skill
is the entrypoint that orchestrates the whole pipeline; the
planning runbook owns the
sequence and the gates, and each stage's craft lives in its own sibling
skill.
Rundown orchestrates workflow; it does not store craft. This skill names the pipeline and points at the stages — it does not duplicate them.
write-plan runbook. The stage stops the pipeline on failure.review-plan runbook inline. It stops the pipeline on failure.execute-plan runbook inline and completes the
pipeline on success.Every stage stops the pipeline on failure (FAIL ANY STOP); the final stage
completes it (PASS ALL COMPLETE).
Use when stepping through a Rundown runbook that is already active or has just been started, when receiving delegation instructions with a claim token, or when rundown CLI commands appear in step output. For cold-start "run the X runbook" requests with nothing active, the rundown launcher skill starts the runbook first.
Use when orchestrating multi-agent work through rundown delegation, dispatching substeps to child agents, or managing delegation tokens
Use when running the Rundown end-to-end test runbook and reporting structured feedback on the workflow.
Use when implementing a written plan task-by-task — the per-task cycle, commit discipline, and escalation rules that an execute-plan runbook orchestrates around.
Use when running the full plan → review → execute pipeline — write the plan, review it, then implement it behind review and verify gates. The top-level entrypoint that orchestrates writing-plans, plan review, and executing-plans end to end.
Use when asked to run or start a Rundown runbook by name (e.g. "run the planning runbook", "start the deploy runbook") and no runbook is active yet. The launcher that resolves a runbook and begins execution. Invocable as /rundown <runbook>.