Menú
Use when running the Rundown end-to-end test runbook and reporting structured feedback on the workflow.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
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 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>.
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
Basado en la clasificación ocupacional SOC
| name | end-to-end-testing |
| description | Use when running the Rundown end-to-end test runbook and reporting structured feedback on the workflow. |
Run the end-to-end test through Rundown state; do not improvise:
rundown run rundown:end-to-end-test
end-to-end-test/write-file.runbook.md, and end-to-end-test/review-and-collate.runbook.md run locally.end-to-end-test/review-file.runbook.md and end-to-end-test/collate-files.runbook.md are delegated by the review wrapper.Only nested review and collation runbooks are delegated. If the wrapper completes before collate, report a defect; never delegate collation from the parent.
--text (human-only, not part of the agent protocol).rundown run, rundown pass, rundown fail, rundown claim, and rundown collect output as the next context. Parent-side pass/fail/collect carry --claim-id <claim_id> (from rundown run's runbook_started event); child-side commands carry the claim_id from rundown claim.rundown status only to recover orientation after an error or interruption..rundown.The DELEGATE step auto-issues a claim token (delegations in rundown status). Claim it:
rundown claim <token> # returns claim_id; dispatch the child to a subagent
Advance each claimed-child step with rundown pass --claim-id <claim_id> / rundown fail --claim-id <claim_id>; prompted child steps need this claim-id transition. On a delegation-exposed run, a bare rundown pass/rundown fail is refused with ACTOR_CONTEXT_REQUIRED even after claiming (exposure is sticky). The orchestrator's own rundown pass --claim-id <claim_id> parent advance is refused OPEN_DELEGATED_CHILDREN while a claimed child is open — wait for the child to report (or rundown abort <token> --claim-id <claim_id> --force). (A --run-targeted mutation is separately refused ACTOR_CONTEXT_REQUIRED: --run is target selection only, not mutation authority.)
On its final step, the child reports its result to the delegation linkage and stops driving the parent. The parent advances only after the orchestrator runs rundown collect --claim-id <parent_claim_id>.
Use rendered {{ path Alias }} paths.
Expected artifacts:
PlanSchemaPathPlanPathReviewSchemaPathReviewPathReviewPathsCollatedReviewPathFeedbackPathDo not rediscover paths or add artifact-only steps. Missing/wrong variables and write-one/check-another mismatches are defects.
Feedback must be JSON matching review.schema.json. Use empty items for no findings.
Capture only concrete issues: unclear prompts, wrong delegation boundary, missing/wrong artifact variables, schema mismatches, required manual inference, failed commands with output.