runbook-writing-wasp-drone — Claude Code subagent
The runbook-writing-wasp-drone subagent writes and audits operational runbooks with exact commands, decision branches, rollback steps, escalation paths, and test status.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install platform-and-release-tools@wasp-nestWhat runbook-writing-wasp-drone does
runbook-writing-wasp-drone handles the authoring and upkeep of operational runbooks used when alerts fire. It first sorts a request into break-fix, scheduled operation, or diagnostic work, then builds a linear procedure with explicit IF/THEN branches. Commands, URLs, variables, and decision points are checked for hidden assumptions.
The subagent requires copy-ready commands with exact flags, namespaces, and service names. Each state-changing action gets an undo step or an explicit irreversible-action note, while every runbook includes a named escalation contact and response expectation. It records the latest exercise environment and outcome, links related postmortems, and applies a completion checklist. Untested documents receive a prominent TEST STATUS: UNTESTED marker.
Its scope is the document’s structure, content, testability, and freshness. It does not configure PagerDuty or OpsGenie and does not own infrastructure decisions. Codex uses .codex/agents/runbook-writing-wasp-drone.toml, so its setup differs from Claude Code.
What it helps with
- write a runbook for an alert
- audit commands and decision branches
- document rollback for state-changing actions
- define an escalation contact and route
- turn a postmortem into a tested procedure
Example prompts for the agent
- Write a runbook for this alert with exact commands, IF/THEN branches, and rollback steps.
- Audit this runbook for hidden context and add a concrete escalation path.
- Turn this postmortem into a runbook and define a game day test.
How to install runbook-writing-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nest2Manually: put the files in place
.claude/agents/runbook-writing-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/runbook-writing-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/runbook-writing-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about runbook-writing-wasp-drone
How do I install runbook-writing-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install platform-and-release-tools@wasp-nest, and add .claude/agents/runbook-writing-wasp-drone.md.
What does runbook-writing-wasp-drone do?
It writes and audits operational runbooks with exact commands, explicit branches, rollback coverage, escalation details, and test status. It can also connect procedures to postmortems and apply a readiness checklist.
What is outside this subagent’s scope?
It does not configure PagerDuty or OpsGenie, and it does not make infrastructure decisions. Those requests are routed to other subagents.