Process Doc
- 2.1k installs
- 23.1k repo stars
- Updated July 28, 2026
- anthropics/knowledge-work-plugins
process-doc is an agent skill that Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, b.
About
If you see unfamiliar placeholders or need to check which tools are connected see CONNECTORS md CONNECTORS md Document a business process as a complete standard operating procedure SOP 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 markdown Process Document Process Name Owner Person Team Last Updated Date Review Cadence Quarterly Annually Purpose Why this process exists and what it accomplishes The process doc agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation
- description: Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in some
- argument-hint: "<process name or description>"
- > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md
- Follow process-doc SKILL.md steps and documented constraints.
- Follow process-doc SKILL.md steps and documented constraints.
Process Doc by the numbers
- 2,123 all-time installs (skills.sh)
- +92 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #508 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
process-doc capabilities & compatibility
- Capabilities
- description: document a business process — flowc · argument hint: "<process name or description>" · > if you see unfamiliar placeholders or need to · follow process doc skill.md steps and documented
- Use cases
- orchestration
What process-doc says it does
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 hando
argument-hint: "<process name or description>"
> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill process-docAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.1k |
|---|---|
| repo stars | ★ 23.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | anthropics/knowledge-work-plugins ↗ |
When should an agent use process-doc and what problem does it solve?
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,
Who is it for?
Developers invoking process-doc as documented in the skill source.
Skip if: Skip when requirements fall outside process-doc documented scope.
When should I use this skill?
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,
What you get
Outputs aligned with the process-doc SKILL.md workflow and stated deliverables.
- Standard operating procedure
- RACI matrix
- Process flowchart
By the numbers
- Produces 3 core artifacts per process: SOP, RACI matrix, and flowchart
Files
/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
1. Start messy — You don't need a perfect description. Tell me how it works today and I'll structure it. 2. Include the exceptions — "Usually we do X, but sometimes Y" is the most valuable part to document. 3. Name the people — Even if roles change, knowing who does what today helps get the process right.
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la462k185k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.379k15.8k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.378k92.5k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.375k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k8How it compares
Pick Process Doc for operational SOPs and RACI; use architecture-documentation skills when the deliverable is system design not business process.
FAQ
What is process-doc?
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
When should I use process-doc?
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
Is process-doc safe to install?
Review the Security Audits panel on this page before production use.