Agent Skills
› anthropics/knowledge-work-plugins
› process-doc
process-doc
GitHub将头脑中的业务流程转化为标准操作程序(SOP)，生成流程图、RACI矩阵及异常处理指南。适用于流程标准化、明确责任归属、审计合规及捕获实际工作细节。
Trigger Scenarios
需要正式化存在于个人头脑中的业务流程
构建RACI矩阵以明确职责归属
编写用于交接或审计的标准操作程序(SOP)
记录工作流程中的例外情况和边缘案例
Install
npx skills add anthropics/knowledge-work-plugins --skill process-doc -g -y
SKILL.md
Frontmatter
{
"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.
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.
Version History
- 6f13415 Current 2026-07-05 18:30
