Process Doc
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The process-doc skill transforms informal knowledge about business workflows into structured, professional documentation. By guiding users through a discovery process, it captures essential operational details, including roles, responsibilities, step-by-step instructions, and edge-case handling. The output is a standardized SOP format that includes a RACI matrix, process flow, and performance metrics, ensuring that tribal knowledge is effectively codified for team alignment, audits, or handoffs.
What it does
- Generates comprehensive Standard Operating Procedures (SOPs) from informal input.
- Creates RACI matrices to define ownership and stakeholder involvement.
- Maps out process flows using step-by-step descriptions or ASCII diagrams.
- Identifies and documents exceptions and edge cases for robust process coverage.
- Defines success metrics and measurement methods for the documented process.
- Integrates with knowledge bases and project trackers to update existing docs or create actionable tasks.
When to use it
- When formalizing a process that currently exists only as tribal knowledge.
- When you need to clarify roles and responsibilities within a team.
- When preparing for an audit or a formal handoff of responsibilities.
- When you need to capture how work is actually performed, including common exceptions.
Advantages
- Reduces ambiguity by clearly assigning roles and responsibilities.
- Standardizes documentation across the organization.
- Captures critical edge cases that are often missed in informal descriptions.
- Facilitates easier onboarding and process improvement initiatives.
- Provides a clear framework for measuring process success.
Usage examples
- “Document our monthly client billing process.”
- The agent will ask clarifying questions about the billing steps, stakeholders, and common issues, then generate a full SOP including a RACI matrix and metrics table.
- “Create an SOP for how we handle urgent bug reports from customers.”
- The agent will structure the workflow for triaging and resolving urgent bugs, identifying who is responsible for each stage and how to handle exceptions like out-of-hours reports.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/process-doc/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip process-doc.zip -d .agents/skills
Documentation by Anthropic
/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 $ARGUMENTSHow 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.
Files
- ATTRIBUTION.mdAdded by AutoGineer899 B
- LICENSELicence file added by AutoGineer11.3 KiB
- SKILL.md2.4 KiB
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · operations/skills/process-doc · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download process-doc.zip