process-doc
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/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).
如果你看到不熟悉的占位符或需要查看已连接的工具，请参阅CONNECTORS.md。
将业务流程记录为完整的标准作业程序（SOP）。
Usage
使用方法
/process-doc $ARGUMENTS/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.
逐步引导你梳理流程——你可以描述流程、粘贴现有文档，或者只需告诉我流程名称，我会提出合适的问题。最终我会生成一份完整的SOP。
Output
输出结果
markdown
undefinedmarkdown
undefinedProcess 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
RACI矩阵
| 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]
[ASCII流程图或分步说明]
Detailed Steps
详细步骤
Step 1: [Name]
步骤1：[名称]
- Who: [Role]
- When: [Trigger or timing]
- How: [Detailed instructions]
- Output: [What this step produces]
- 责任人：[角色]
- 触发时机：[触发条件或时间]
- 操作方式：[详细说明]
- 输出结果：[该步骤产生的成果]
Step 2: [Name]
步骤2：[名称]
[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]
undefined- [相关流程或政策链接]
undefinedIf 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
如果已连接~~知识库：
- 搜索现有流程文档进行更新，避免重复创建
- 将完成的SOP发布到你的维基站点
如果已连接~~项目跟踪工具：
- 将流程与相关项目和工作流关联
- 创建流程改进行动项的任务
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.
- 无需完美起步——你不需要提供完美的流程描述。告诉我当前的实际操作方式，我会帮你整理结构。
- 务必包含异常情况——“通常我们做X，但有时会做Y”是文档中最有价值的部分。
- 明确具体人员——即使角色会变动，了解当前的职责分工有助于确保流程的准确性。