process-doc
/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 a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.
- Author
- anthropics ↗
- Repository
- knowledge-work-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Arguments
/process-doc <process name or description>
Original author 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.
How it works
- Usage
- How It Works
- Output
- If Connectors Available
- Tips
SKILL.md preview
--- 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](../../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 ```markdown ## 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · anthropics/knowledge-work-plugins | 100 | Apache-2.0 |
| SkillMedev/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 449b058fbeee (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100keel-process
Document or redesign a business process — standard operating procedure (SOP), process map, RACI, and owner assignment. Use when asked to "document this process", "write a runbook", "design how we handle X", or "map the process for Y". - 100okhp3-raci-governance-matrix
Generate and validate a RACI matrix and governance responsibility document from a validated PNS. Use this skill when the user needs a standalone RACI chart, a governance matrix, or a responsibility assignment document for a process; when they ask to produce a RACI table,… - 100okhp3-sop-work-instructions
Generate Standard Operating Procedures (SOPs) and work instructions from a validated PNS. Use this skill when the user needs to produce a human-readable procedure document from a process narrative; when they ask to write an SOP, create work instructions, generate a procedure, or… - 100process-documentation-sop
Turns a process that lives in one person's head into a standard operating procedure someone new can follow without asking: the current-state map built by observation, then the document with purpose, trigger, owner, roles, numbered steps naming the exact system and the expected… - 100sop-builder
Use when a repeated process lives in one person's head, breaks when they are away, gets re-explained to every new hire, or produces inconsistent results — and needs writing down once so anyone or any agent can run it the same way. Also for auditing and rewriting an SOP that is… - 100raci-matrix
Use when ownership, approval rights, handoffs, or decision authority are unclear. Use when applying the RACI Matrix consulting method and when a user asks for RACI Matrix, method execution, structured diagnosis, or action planning.