Individual skill
process-doc
Documents recurring processes as step-by-step SOPs with decision points, edge cases, and a named owner, so anyone can run the process correctly without asking. Use when someone asks "write an SOP for this", "document our onboarding process", "this only lives in one person's head", or wants to delegate a recurring task safely. Do NOT use for incident-response or on-call operational runbooks - use runbook-writer instead; for customer-facing product documentation, use help-documentation.
skills/process-doc/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- operations Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Process Documentation
A Standard Operating Procedure lets anyone perform a recurring process correctly without asking. The costly failure it prevents is silent: the one person who knows the process leaves, gets sick, or goes on vacation, and the team discovers the "documented" process was actually tribal knowledge. Good SOPs reduce errors, enable delegation, and survive turnover - but only if they cover the branches, not just the happy path.
## Operating procedure
Follow the steps in order: qualify before writing (most processes do not deserve an SOP), and validate before publishing (an untested SOP is a rumor with formatting).
### Step 1: Qualify the process
Write an SOP only when at least two of these hold; otherwise the documentation cost exceeds the risk:
- The process runs weekly or more often, or will be run by more than one person.
- A mistake costs more than an hour of rework, money, or customer trust.