process-doc
流程文档化指南,帮助记录和优化工作流程,AI Agent Skill,提升工作效率和自动化能力
npx skills add anthropics/knowledge-work-plugins --skill process-docBefore / After 效果对比
1 组手动完成流程文档化指南,帮助记录和优化相关任务,需要反复查阅文档和调试,整个过程大约需要34分钟
使用该 Skill 自动化处理,5分钟内完成,流程标准化且准确率高
description SKILL.md
process-doc
/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.
Weekly Installs294Repositoryanthropics/know…-pluginsGitHub Stars10.5KFirst SeenMar 13, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled oncodex279gemini-cli277opencode277cursor276github-copilot275amp275
forum用户评价 (0)
发表评价
暂无评价,来写第一条吧
统计数据
用户评分
为此 Skill 评分