Document Operational Procedures and Runbooks

Creates runbooks, SOPs, playbooks, and technical documentation with a universal structure that emphasizes Definition of Done, specificity, action-first steps, and decision clarity. It prevents the common documentation failures of vague language, passive voice, walls of text, and unmaintainable documentation.

Choose the right format for your use case (Runbook for incidents, Deployment Playbook for releases, Standard SOP for any repeatable process, Troubleshooting Guide for debugging, etc.). The skill guides you through creating a document with a universal structure: 1. Definition of Done checklist (complete when...). 2. When to Use This. 3. Prerequisites. 4. The Process (numbered action-first steps). 5. Verify Completion. 6. When Things Go Wrong. 7. Questions/Contact. Output: A scannable, actionable document with clear success criteria, no ambiguous language, specific thresholds/names, and clear decision points instead of vague heuristics.

Templates stored in references/ directory. Supports Markdown and can be exported to other formats. Include metadata (title, owner, last_updated, review_schedule) but skip unnecessary fields like version matrices or approval chains. Quality checklist ensures unfamiliar readers can follow without asking questions and all steps are testable.