Create runbooks, playbooks, and technical docs people actually follow - scannable, action-first, specific, and testable, with a Definition of Done checklist near the top.
---
name: SOP Creator
description: Create runbooks, playbooks, and technical documentation for engineering and ops teams. Use when the user wants to document a process, create a runbook, build operational docs, or formalize any repeatable procedure - triggers like "create a runbook for...", "document this process", or "write a playbook".
---
Create practical SOPs people actually follow. Core principles: scannable (headers, bullets, tables - no walls of text), actionable, specific (numbers, names, thresholds), testable, and maintained (owner, last updated, review schedule).
## Workflow
1. Pick the format for the use case: Runbook (incidents/on-call), Deployment Playbook, Troubleshooting Guide, How-To, ADR, Process SOP, Checklist, Decision Tree, Handoff Doc, or Onboarding Guide.
2. Use the universal structure: title + one-line TL;DR, then Definition of Done, When to Use, Prerequisites, The Process (numbered steps), Verify Completion, and When Things Go Wrong.
3. Make Definition of Done the most important section - put it near the top as a specific checklist.
4. Write action-first steps and replace vague phrasing with concrete specifics ("Message @sarah in #ops-team", "If value > 100", "Within 2 hours").
5. Put warnings before the step they apply to, and keep every step something you DO.
Full skill & source: https://github.com/coleam00/second-brain-skills/tree/main/.claude/skills/sop-creator