Loading...
Loading...
Create runbooks, playbooks, and technical documentation for engineering teams. Use when the user wants to document a process, create a runbook, build operational docs, or formalize any repeatable technical procedure. Triggers on requests like "create a runbook for...", "document this process", "write a playbook", or any technical documentation request.
npx skill4agent add coleam00/second-brain-skills sop-creator| Type | When to Use |
|---|---|
| Runbook | Emergency response, incidents, on-call |
| Deployment Playbook | Releases, migrations, maintenance |
| Troubleshooting Guide | Debugging, diagnosis trees |
| How-To Guide | One-off setup, configuration |
| ADR | Architecture decisions |
| Type | When to Use |
|---|---|
| Process SOP | Repeatable business workflows |
| Checklist | Quality control, verification |
| Decision Tree | Complex if/then scenarios |
| Handoff Doc | Role transitions, shift changes |
| Type | When to Use |
|---|---|
| Production Workflow | Content creation pipelines |
| Review Process | Approval workflows |
| Publishing Checklist | Pre-launch verification |
| Type | When to Use |
|---|---|
| Standard SOP | Any repeatable process |
| Quick Reference | Condensed version of longer SOP |
| Onboarding Guide | New person ramping up |
# [What This Does]
> **TL;DR:** One sentence - what, when, who.
## Definition of Done
This is complete when:
- [ ] [Primary outcome]
- [ ] [Verification step]
- [ ] [Any handoff/notification]
## When to Use This
[Trigger conditions]
## Prerequisites
[What you need before starting]
## The Process
[Numbered steps - the actual work]
## Verify Completion
[Return to Definition of Done, confirm all checked]
## When Things Go Wrong
[Common issues and fixes]
## Questions?
[Who to contact]| Don't Write | Write Instead |
|---|---|
| "Contact the team" | "Message @sarah in #ops-team" |
| "Wait until ready" | "Wait until status shows 'Complete' (~5 min)" |
| "Review carefully" | "Check items A, B, C in the dashboard" |
| "As appropriate" | "If value > 100" |
| "Regularly" | "Every Monday at 9am" |
| "Soon" | "Within 2 hours" |
# Bad
"The report should be reviewed before sending to ensure
accuracy and completeness of all data fields."
# Good
1. Open the report in [System]
2. Verify these fields are populated:
- [ ] Customer name
- [ ] Amount
- [ ] Date
3. Click "Send"# Bad
1. Delete the old records
Note: This cannot be undone
# Good
> **WARNING:** This permanently deletes records. Export first if needed.
1. Delete the old records# Bad
"Handle the request based on priority level"
# Good
**If priority is:**
- **Critical:** Drop everything, handle now, notify manager
- **High:** Handle within 4 hours
- **Normal:** Handle within 24 hours
- **Low:** Add to weekly batch---
title: [Clear name]
owner: [Person or team]
last_updated: [Date]
review_schedule: [quarterly/annually/as-needed]
---references/| Template | Use For |
|---|---|
| runbook.md | Incidents, emergencies, on-call |
| standard-sop.md | Any repeatable process |
| how-to-guide.md | One-off tasks, setup |
| onboarding-guide.md | New person ramping up |
| decision-tree.md | Complex if/then flows |
| checklist.md | QC, verification |