Process Documentation
OfficialFreeStreamline your business processes with structured SOPs.
Free · Opens the source repo
What Process Documentation does
The Process Documentation skill helps users formalize and document business processes in a structured manner. It is designed for teams looking to clarify ownership, create standard operating procedures (SOPs), and capture the nuances of how work is done. By guiding users through the documentation process, this skill ensures that essential details are not overlooked, making it easier to onboard new team members and maintain consistency in operations.
Users can initiate the documentation process by providing a description of the workflow or existing documentation. The skill then prompts for specific information, producing a comprehensive SOP that includes a RACI matrix, detailed steps, exceptions, and metrics. This structured output not only serves as a reference for current practices but also helps in identifying areas for improvement.
This skill is particularly useful for project managers, team leaders, and anyone involved in process improvement initiatives. It allows teams to document processes that may currently exist only in someone's mind, ensuring that knowledge is captured and shared across the organization. Additionally, if connected to a knowledge base or project tracker, it can leverage existing documentation and link processes to relevant projects, enhancing workflow integration.
Overall, the Process Documentation skill is an invaluable tool for organizations aiming to improve clarity, accountability, and efficiency in their operations.
When to use it
Use this skill when you need to formalize a business process, create SOPs, or clarify roles and responsibilities.
When not to use it
This skill may not be suitable for informal or rapidly changing processes that do not require documentation.
What you can build with it
Onboarding New Team Members
Use the skill to create SOPs that new hires can reference to understand their roles and responsibilities.
Process Improvement Initiatives
Document current workflows to identify inefficiencies and areas for enhancement in team processes.
Compliance and Auditing
Generate detailed SOPs that can be used for compliance checks and audits, ensuring all processes are well-documented.
How to install Process Documentation
View source1. Install with the skills CLI
npx skills add anthropics/knowledge-work-plugins/process-doc --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by anthropics/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.
Frequently asked questions about Process Documentation
Similar skills
Competitive Analysis
Build detailed competitive landscape decks efficiently.
Brand Discovery
Structured interviews to articulate brand identity.
CrossFrame Org
Facilitates structured organizational analysis and repair.
Technical Product Pricing
Optimize your pricing strategy for technical products.
Product-Led Growth
Optimize your go-to-market strategy with data-driven insights.
Positioning Strategy
Own your market position with clear differentiation.