crew-runbooks

Writes and maintains symptom-indexed operational runbooks for deploys, rollbacks, and incident response.

2|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill crew-runbooks-mbadali25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crew-runbooks
Source: https://github.com/mbadali25/useful-claude-add-ons/tree/main/plugin/crew/skills/crew-runbooks
Command: npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill crew-runbooks-mbadali25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operational procedures often live only in one engineer's head, so when something breaks at 3am nobody knows the exact commands to run. This Skill captures deploys, rollbacks, alert responses, and disaster recovery steps as verified, copy-pasteable runbooks indexed by symptom. ## Core Features & Use Cases - Runbook Authoring: Generates short, step-by-step runbooks in docs/runbooks/ with exact commands, verification lines after destructive steps, named escalation paths, and rollback-of-the-rollback instructions. - Symptom-First Index: Maintains docs/runbooks/INDEX.md keyed by observable symptom rather than system name, so only the index and one relevant runbook are loaded into context. - Verification Tracking: Stamps every runbook with last verified metadata and audits entries not verified in 90 days or referencing resources that no longer exist. - Use Case: After resolving an incident where inventory files stopped loading, ask the Skill to draft a rollback runbook from the actual commands run in the session, then add it to the symptom index marked last verified: NEVER until someone executes it end to end. ## Quick Start Ask the assistant to write a runbook for rolling back the inventory loader Lambda, including verification steps and an escalation contact.

Frequently Asked Questions about crew-runbooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an operational runbook for deployments and rollbacks?

Create a Markdown file in docs/runbooks named verb-thing.md with numbered, copy-pasteable commands, a verify line after every destructive step, a named escalation contact, and a rollback-of-the-rollback section. Keep it short enough to follow on a phone.

How should runbooks be indexed for on-call incident response?

Index runbooks by symptom rather than by system in an INDEX.md file, since at 3am you know what you are seeing, not which component failed. Load only the index by default, then read the single relevant runbook.

When should a runbook not be written?

Skip a runbook when tooling already performs the whole procedure, such as a single make deploy command. Runbooks are for repeatable, destructive, or pressure-prone procedures that someone would get wrong without documentation.

How do I keep runbooks from going stale?

Stamp each runbook with a last-verified date and author, then run an audit that flags entries unverified for 90 days or referencing resources that no longer exist. Verification means actually executing the procedure, not just reviewing it.

Can runbooks be generated from a real incident or session?

Yes. Draft the runbook from the commands actually run in the session transcript, validation config, and infrastructure definitions for resource names. Mark it last verified: NEVER until someone runs it end to end.