From operations
Documents business processes with flowcharts, RACI matrices, and SOPs. Use to formalize undocumented processes, clarify ownership, or capture exceptions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/operations:process-doc <process name or description><process name or description>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Document a business process as a complete standard operating procedure (SOP).
/process-doc $ARGUMENTS
Walk me through the process — describe it, paste existing docs, or just tell me the name and I'll ask the right questions. I'll produce a complete SOP.
## Process Document: [Process Name]
**Owner:** [Person/Team] | **Last Updated:** [Date] | **Review Cadence:** [Quarterly/Annually]
### Purpose
[Why this process exists and what it accomplishes]
### Scope
[What's included and excluded]
### RACI Matrix
| Step | Responsible | Accountable | Consulted | Informed |
|------|------------|-------------|-----------|----------|
| [Step] | [Who does it] | [Who owns it] | [Who to ask] | [Who to tell] |
### Process Flow
[ASCII flowchart or step-by-step description]
### Detailed Steps
#### Step 1: [Name]
- **Who**: [Role]
- **When**: [Trigger or timing]
- **How**: [Detailed instructions]
- **Output**: [What this step produces]
#### Step 2: [Name]
[Same format]
### Exceptions and Edge Cases
| Scenario | What to Do |
|----------|-----------|
| [Exception] | [How to handle it] |
### Metrics
| Metric | Target | How to Measure |
|--------|--------|----------------|
| [Metric] | [Target] | [Method] |
### Related Documents
- [Link to related process or policy]
If ~~knowledge base is connected:
If ~~project tracker is connected:
npx claudepluginhub anthropics/knowledge-work-plugins --plugin operations3plugins reuse this skill
First indexed Jun 13, 2026
Transforms unstructured process descriptions into clear, actionable Standard Operating Procedures written at a 5th-grade reading level. Checks for business context and asks clarifying questions to fill gaps.
Visualizes and documents business processes (AS-IS/TO-BE) to identify inefficiencies, bottlenecks, and improvement opportunities. Useful for workflow analysis, automation planning, and team onboarding.
Writes operational artifacts (SOPs, process docs, runbooks, handoff docs, onboarding guides) for non-technical and cross-functional teams. Useful when users describe repeatable workflows they want documented.