Skills › Knowledge Work Plugins › process-doc

process-doc

skill · 82 lines · Apache-2.0 · operations/skills/process-doc/SKILL.md

The facts

Its 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.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent picks this skill when someone wants a business process written down formally — turning a process that lives in someone's head into a structured SOP, building a RACI to settle who owns what, or capturing the exceptions and edge cases of how work really gets done. It is invoked by a person describing or naming a process, not by another skill.

Things a person might say (the model's guesses)

“Write up our customer onboarding process as an SOP”
“Build a RACI for the invoice approval workflow — nobody agrees who owns what”
“Document how we handle refund exceptions, it's all in Dana's head right now”

A model's summary of when it is used.

A model's reading

What it takes when started

What to type after its name when you start it.

From its settingsline 4

Licence

Apache-2.0, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Uses an outside tool

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---

2name: process-doc

3description: 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.

4argument-hint: "<process name or description>"

5---

7# /process-doc

9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).

11Document a business process as a complete standard operating procedure (SOP).

/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).

Raw lines 1 to 12

Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close

13## Usage

15```

16/process-doc $ARGUMENTS

17```

19## How It Works

21Walk 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.

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.

Raw lines 19 to 22

23## Output

25```markdown

26## Process Document: [Process Name]

27**Owner:** [Person/Team] | **Last Updated:** [Date] | **Review Cadence:** [Quarterly/Annually]

29### Purpose

30[Why this process exists and what it accomplishes]

32### Scope

33[What's included and excluded]

35### RACI Matrix

37|------|------------|-------------|-----------|----------|

40### Process Flow

41[ASCII flowchart or step-by-step description]

43### Detailed Steps

45#### Step 1: [Name]

46- **Who**: [Role]

47- **When**: [Trigger or timing]

48- **How**: [Detailed instructions]

49- **Output**: [What this step produces]

51#### Step 2: [Name]

52[Same format]

54### Exceptions and Edge Cases

55| Scenario | What to Do |

56|----------|-----------|

57| [Exception] | [How to handle it] |

59### Metrics

60| Metric | Target | How to Measure |

61|--------|--------|----------------|

62| [Metric] | [Target] | [Method] |

64### Related Documents

65- [Link to related process or policy]

66```

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]

Raw lines 23 to 67

68## If Connectors Available

70If **~~knowledge base** is connected:

71- Search for existing process documentation to update rather than duplicate

72- Publish the completed SOP to your wiki

74If **~~project tracker** is connected:

75- Link the process to related projects and workflows

76- Create tasks for process improvement action items

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

Raw lines 68 to 77

Uses an outside tool ~~knowledge :70

Uses an outside tool ~~project :74

78## Tips

801. **Start messy** — You don't need a perfect description. Tell me how it works today and I'll structure it.

812. **Include the exceptions** — "Usually we do X, but sometimes Y" is the most valuable part to document.

823. **Name the people** — Even if roles change, knowing who does what today helps get the process right.

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.

Raw lines 78 to 82

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.