Sop writer

Skill serejaris/kimi-skills/skills/sop-writer

Полная коллекция скиллов Kimi (267 built-in + 7 plugin skills), выгруженная из сандбокса агента

Install

npx -y skills add serejaris/kimi-skills --skill sop-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

将业务流程梳理成完整的标准操作流程文档（SOP），包括流程图、RACI分工矩阵、详细操作步骤以及异常情况处理。当用户需要将隐性经验显性化、明确岗位职责、规范工作交接、或记录特殊场景和边界情况时触发，例如用户提及“梳理流程”、“制定SOP”、“明确分工”、“规范操作”或直接描述一个流程名称。

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, as published. Nobody here has run it

/sop-writer

将业务流程梳理为完整的标准操作流程文档（SOP）。

用法

/sop-writer $ARGUMENTS

工作方式

向我描述你的流程——可以直接说明、粘贴现有文档，或者只告诉我流程名称，我会通过提问帮你理清。最终我会产出一份完整的 SOP 文档。

输出格式

## 流程文档：[流程名称]
**负责人：** [个人/团队] | **最后更新：** [日期] | **审核周期：** [每季度/每年]

### 目的
[该流程存在的原因及其目标]

### 范围
[包含和不包含的内容]

### RACI 矩阵
| 步骤 | 执行者（R） | 决策者（A） | 咨询方（C） | 知会方（I） |
|------|------------|-------------|-----------|----------|
| [步骤] | [谁执行] | [谁负责] | [咨询谁] | [通知谁] |

### 流程图
[ASCII 流程图或逐步说明]

### 详细步骤

#### 步骤 1：[名称]
- **谁**：[角色]
- **何时**：[触发条件或时间节点]
- **如何**：[详细操作说明]
- **产出**：[该步骤的输出物]

#### 步骤 2：[名称]
[同上格式]

### 异常与边界情况
| 场景 | 处理方式 |
|----------|-----------|
| [异常情况] | [处理办法] |

### 指标
| 指标 | 目标值 | 衡量方式 |
|--------|--------|----------------|
| [指标] | [目标] | [方法] |

### 相关文档
- [相关流程或政策的链接]

使用技巧

先说再理 — 不需要一开始就描述得很完美。先告诉我今天是怎么做的，我来帮你整理结构。
把例外说出来 — "通常我们做 X，但有时候会做 Y"，这恰恰是最值得文档化的部分。
点名到人 — 即使角色会轮换，知道今天是谁在做什么，有助于把流程理清楚。