process-doc
anthropics/knowledge-work-plugins
Document business processes as complete SOPs with flowcharts, RACI matrices, and exception handling.
What is process-doc?
Formalizes undocumented processes into structured standard operating procedures (SOPs). Use this when capturing how work actually gets done, clarifying ownership via RACI matrices, or creating handoff documentation for audits and team transitions.
- Generate complete SOPs with purpose, scope, and detailed step-by-step instructions
- Create RACI matrices to clarify who is responsible, accountable, consulted, and informed
- Document process flows with ASCII flowcharts or narrative descriptions
- Capture exceptions and edge cases that represent how work actually happens
- Define metrics and success measures for process execution
- Link related documents and processes for cross-reference
How to install process-doc
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill process-docHow to use process-doc
- 1.Run /process-doc with the process name or description
- 2.Describe the process—paste existing docs, name it, or explain how it works today
- 3.Provide details about roles, triggers, timing, and outputs for each step
- 4.Mention exceptions, workarounds, and edge cases that occur in practice
- 5.Review the generated SOP and refine as needed
Use cases
- Formalizing a process that currently lives only in someone's head or scattered across emails
- Building a RACI matrix to resolve confusion about who owns what in a workflow
- Writing an SOP for onboarding new team members or handing off responsibilities
- Documenting exceptions and workarounds that have evolved in practice
- Creating audit-ready process documentation for compliance or review
- Operations managers and process owners
- Team leads managing handoffs and transitions
- Compliance and audit professionals
- Business analysts documenting workflows
- Anyone formalizing informal processes
process-doc FAQ
No. Start messy—describe how the process works today and the skill will structure it into a proper SOP.
Document scenarios where the standard process doesn't apply and how to handle them. These edge cases are often the most valuable part of the documentation.
If a knowledge base is connected, the skill will search for existing documentation to update rather than duplicate.
A markdown document with purpose, scope, RACI matrix, process flow, detailed steps, exceptions table, metrics, and related documents.
If a project tracker is connected, the skill can link the process to related projects and create improvement action items.
Full instructions (SKILL.md)
Source of truth, from anthropics/knowledge-work-plugins.
name: process-doc description: Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done. argument-hint: "<process name or description>"
/process-doc
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).
Usage
/process-doc $ARGUMENTS
How It Works
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.
Output
## 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 Connectors Available
If ~~knowledge base is connected:
- Search for existing process documentation to update rather than duplicate
- Publish the completed SOP to your wiki
If ~~project tracker is connected:
- Link the process to related projects and workflows
- Create tasks for process improvement action items
Tips
- Start messy — You don't need a perfect description. Tell me how it works today and I'll structure it.
- Include the exceptions — "Usually we do X, but sometimes Y" is the most valuable part to document.
- Name the people — Even if roles change, knowing who does what today helps get the process right.
Related skills
More from anthropics/knowledge-work-plugins and the wider catalog.
process-optimization
Analyze and improve business processes by identifying bottlenecks, waste, and optimization opportunities.
product-brainstorming
Sharp product thinking partner for brainstorming, problem exploration, and stress-testing ideas.
prospect
Convert ICP descriptions to ranked, enriched lead lists with emails and phone numbers via Apollo.
quarterly-review
Generates a full QBR narrative — revenue trend, margin trend, customer health, top opportunities and risks — as a presentation-ready PDF or deck. Accepts optional quarter and save-to arguments.
reconciliation
Compare GL balances to subledgers, bank statements, or third-party data to identify and resolve reconciling items.
recruiting-pipeline
Track candidates through sourcing, screening, interviewing, and offer stages with pipeline metrics.