process-docs

---
name: process-docs
description: When the user needs to create SOPs, playbooks, runbooks, or other operational documentation that defines how a recurring process should be executed.
related: [support-docs, board-update]
reads: [startup-context]
---

# Process Documentation

## When to Use
Activate when a founder or operator needs to document an internal process so it can be executed consistently by anyone on the team. This includes prompts like "write an SOP for X," "create a runbook for incident response," "document our onboarding playbook," "how do we standardize this process," or any request to turn tribal knowledge into a repeatable procedure.

## Context Required
- **From startup-context:** company stage, team size, current tools and systems, organizational structure, compliance requirements.
- **From the user:** the process to document, who owns and executes it, current pain points or failure modes, frequency of execution, tools involved, and whether this replaces an existing (undocumented) process or is net-new.

## Workflow
1. **Identify document type** - Determine whether this is an operational SOP (routine procedure), an incident runbook (reactive response), or an onboarding playbook (sequential learning path). Each uses a different template.
2. **Map the process end-to-end** - Walk through every step from trigger event to completion. Identify inputs, outputs, decision points, handoffs, and escalation paths.
3. **Define ownership and RACI** - Assign a single owner (Responsible), identify who Approves, who is Consulted, and who is Informed for each major step.
4. **Draft the document** - Write using the appropriate template below. Use imperative voice ("Open the dashboard," not "The dashboard should be opened").
5. **Add decision trees** - For any step with conditional logic, create explicit if/then branches. Never leave ambiguity at a fork.
6. **Include failure modes** - Document what to do when each step fails. A process doc without error handling is incomplete.
7. **Set review cadence** - Specify when this document should be reviewed and by whom (e.g., quarterly by the process owner).
… load the full skill through Skill Me