메뉴
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 직업 분류 기준
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 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>.
Use when converting an existing Claude skill (SKILL.md) into a rundown runbook — distilling the skill's workflow backbone into orchestration steps and artifacts without duplicating the skill's context
| 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. |
Skill(skill: "rundown:running-runbooks")Skill(skill: "rundown:delegating-runbooks") — step 1 delegatesrundown run rundown:planningCapture the run claim from that command: rundown run emits it as runbook_started.claim_id. This pipeline delegates (step 1), so every orchestrator command you issue — collect, pass, goto — must carry --claim-id <claim_id>.
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).