sop-creator
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSOP Creator
SOP生成器
Purpose
目的
Transform unstructured process descriptions into clear, actionable Standard Operating Procedures written at a 5th-grade reading level.
将非结构化的流程描述转化为清晰、可执行的标准操作程序（SOP），内容难度控制在5年级阅读水平。
Execution Logic
执行逻辑
Check $ARGUMENTS first to determine execution mode:
首先检查$ARGUMENTS以确定执行模式：
If $ARGUMENTS is empty or not provided:
若$ARGUMENTS为空或未提供：
Respond with:
"sop-creator loaded, describe the process you want to document"
Then wait for the user to provide their process description in the next message.
回复内容如下：
"sop-creator已加载，请描述您需要文档化的流程"
随后等待用户在后续消息中提供流程描述。
If $ARGUMENTS contains content:
若$ARGUMENTS包含内容：
Proceed immediately to Task Execution (skip the "loaded" message).
直接进入任务执行环节（跳过“已加载”提示消息）。
Task Execution
任务执行
When process description is available (either from initial $ARGUMENTS or follow-up message):
当获取到流程描述后（无论是来自初始$ARGUMENTS还是后续消息）：
1. Check for Business Context
1. 检查业务上下文
Check if exists in the project root.
FOUNDER_CONTEXT.md- If it exists: Read it and use the business context to personalize your output (company name, brand voice, industry specifics, audience, tools used).
- If it doesn't exist: Proceed using defaults from "Defaults & Assumptions".
检查项目根目录下是否存在文件。
FOUNDER_CONTEXT.md- 若存在： 读取该文件并利用其中的业务上下文对输出内容进行个性化调整（如公司名称、品牌语气、行业细节、目标受众、使用工具等）。
- 若不存在： 按照“默认设置与假设”中的内容进行操作。
2. Analyze Initial Input
2. 分析初始输入
From the user's initial description, extract what's available:
- Process name or title
- Who performs this process (role/skill level)
- Tools or systems involved
- Expected outcome or end state
- Any compliance or quality requirements
- Critical steps mentioned
从用户的初始描述中提取以下可用信息：
- 流程名称或标题
- 执行该流程的人员（角色/技能水平）
- 涉及的工具或系统
- 预期结果或最终状态
- 任何合规性或质量要求
- 提及的关键步骤
3. Ask Clarifying Questions (If Needed)
3. 提出澄清问题（如有必要）
Use AskUserQuestion tool to gather missing critical information. Ask a maximum of 5 questions, but fewer is better — stop as soon as you have enough to create a complete SOP.
Question Bank (priority order):
| # | Question | Why it matters | Skip if... |
|---|---|---|---|
| 1 | What is the exact process you want documented? | Defines the scope and title | Process is clearly described |
| 2 | Who will be performing this process? (role, skill level, experience) | Determines language complexity and detail level | User already specified the audience |
| 3 | What tools or systems are involved in this process? | Identifies prerequisites and access requirements | Tools are already listed |
| 4 | What is the successful end result? How do you know the process is done correctly? | Defines quality check criteria and success metrics | Outcome is clearly stated |
| 5 | Are there any compliance requirements, safety concerns, or critical warnings? | Ensures important cautions are included | No regulatory or safety concerns |
Question strategy:
- Ask 2-3 questions per batch using AskUserQuestion
- If the first batch answers provide enough detail, stop asking
- Never ask more than 5 questions total
- Only ask questions that block correct execution
使用AskUserQuestion工具收集缺失的关键信息。最多提出5个问题，越少越好——一旦获取足够信息可创建完整SOP，立即停止提问。
问题库（优先级顺序）：
| 序号 | 问题 | 重要性原因 | 可跳过的情况 |
|---|---|---|---|
| 1 | 您需要文档化的具体流程是什么？ | 明确范围和标题 | 流程已被清晰描述 |
| 2 | 谁将执行此流程？（角色、技能水平、经验） | 决定语言复杂度和细节程度 | 用户已明确指定受众 |
| 3 | 此流程涉及哪些工具或系统？ | 确定前提条件和访问权限要求 | 工具已被列出 |
| 4 | 成功完成的结果是什么？如何判断流程已正确执行？ | 定义质量检查标准和成功指标 | 结果已被清晰说明 |
| 5 | 是否有任何合规要求、安全注意事项或关键警告？ | 确保包含重要的警示内容 | 无监管或安全方面的顾虑 |
提问策略：
- 每次使用AskUserQuestion工具批量提出2-3个问题
- 如果第一批问题的回答提供了足够细节，停止提问
- 总提问数绝不超过5个
- 仅提出会阻碍正确执行的问题
4. Generate the SOP
4. 生成SOP
Using the information gathered, create a complete SOP following the structure in Output Format:
- Write at 5th-grade reading level — short sentences, simple words
- One action per step — no compound instructions
- Start each step with action verbs — "Click", "Open", "Verify", "Enter"
- Include expected results — tell users what they should see
- Add warnings for critical steps — prevent common mistakes
- Create quality checks — define "done" explicitly
利用收集到的信息，按照输出格式中的结构创建完整的SOP：
- 内容难度控制在5年级阅读水平——短句、用词简单
- 每步一个动作——不包含复合指令
- 每步以动作动词开头——如“点击”、“打开”、“验证”、“输入”
- 包含预期结果——告知用户操作后应看到的内容
- 为关键步骤添加警告——避免常见错误
- 设置质量检查环节——明确界定“完成”标准
5. Format and Verify
5. 格式调整与验证
- Structure output according to Output Format section
- Complete Quality Checklist self-verification before presenting output
- Ensure the SOP can be followed by someone unfamiliar with the process
- 按照输出格式部分的要求组织输出内容
- 在呈现输出内容前，完成质量检查表的自我验证
- 确保不熟悉该流程的人员也能遵循此SOP
Writing Rules
写作规则
Hard constraints. No interpretation.
硬性约束，无需额外解读。
Core Rules
核心规则
- Write at a 5th-grade reading level
- Use short sentences (10-15 words maximum)
- Use simple, common words — avoid jargon or explain it immediately
- One action per step — never combine multiple actions
- Start each step with an action verb (Click, Open, Enter, Verify, Check)
- Include the expected result after each critical step
- Never invent steps — only document what was described or confirmed
- 内容难度控制在5年级阅读水平
- 使用短句（最多10-15个单词）
- 使用简单常用词汇——避免行话，若使用需立即解释
- 每步一个动作——绝不合并多个动作
- 每步以动作动词开头（点击、打开、输入、验证、检查）
- 在每个关键步骤后添加预期结果
- 绝不编造步骤——仅记录已描述或确认的内容
SOP-Specific Rules
SOP专属规则
- Title format: "SOP: [Process Name]" (clear and searchable)
- Version info is mandatory — SOPs must be version-controlled
- Prerequisites must be explicit — no hidden requirements
- Quality checks must be measurable — avoid subjective criteria
- Common problems section is required — capture known failure modes
- Tools section must include access/permissions needed
- 标题格式：“SOP: [流程名称]”（清晰且便于搜索）
- 版本信息为必填项——SOP必须进行版本控制
- 前提条件必须明确——无隐藏要求
- 质量检查必须可衡量——避免主观标准
- 必须包含常见问题板块——记录已知的失败场景
- 工具板块必须包含所需的访问权限
Audience Rules
受众适配规则
- Assume zero prior knowledge unless specified otherwise
- Define acronyms on first use
- Explain "why" for non-obvious steps
- Include screenshots placeholders where visual guidance helps
- Add warnings before destructive or irreversible actions
- 除非另有说明，否则假设受众无相关前置知识
- 首字母缩写首次出现时需定义
- 对非显而易见的步骤解释“原因”
- 在需要视觉指导的位置添加截图占位符
- 在具有破坏性或不可逆转的操作前添加警告
Output Format
输出格式
The SOP follows this exact structure:
markdown
undefinedSOP需严格遵循以下结构：
markdown
undefinedSOP: [Process Name]
SOP: [Process Name]
Version: 1.0
Last Updated: [Current Date]
Owner: [Role/Name from context or "Process Owner"]
Audience: [Who uses this SOP]
Version: 1.0
Last Updated: [Current Date]
Owner: [Role/Name from context or "Process Owner"]
Audience: [Who uses this SOP]
1. Purpose
1. Purpose
[One clear sentence describing what this process achieves and why it matters.]
[One clear sentence describing what this process achieves and why it matters.]
2. Who Does This
2. Who Does This
[Role or skill level of person performing this process]
[Role or skill level of person performing this process]
3. Tools You Need
3. Tools You Need
- [Tool 1]
- [Tool 2]
- [Access/permissions required]
- [Tool 1]
- [Tool 2]
- [Access/permissions required]
4. Starting Requirements
4. Starting Requirements
Before you start, make sure:
- [Requirement 1]
- [Requirement 2]
- [Everything you need is ready]
Before you start, make sure:
- [Requirement 1]
- [Requirement 2]
- [Everything you need is ready]
5. Step-by-Step Instructions
5. Step-by-Step Instructions
Step 1: [Action Title]
Step 1: [Action Title]
- [Do this specific action]
- [Do this specific action]
What you should see: [Expected result or outcome]
- [Do this specific action]
- [Do this specific action]
What you should see: [Expected result or outcome]
Step 2: [Action Title]
Step 2: [Action Title]
- [Do this specific action]
- [If needed, add a sub-step for clarity]
- [If needed, add another sub-step]
Warning: [Important thing that could go wrong or caution]
- [Do this specific action]
- [If needed, add a sub-step for clarity]
- [If needed, add another sub-step]
Warning: [Important thing that could go wrong or caution]
Step 3: [Action Title]
Step 3: [Action Title]
- [Do this specific action]
What you should see: [Expected result]
[Continue with numbered steps until process completion...]
- [Do this specific action]
What you should see: [Expected result]
[Continue with numbered steps until process completion...]
6. Quality Check
6. Quality Check
After finishing, verify:
- [Verification item 1 — specific and measurable]
- [Verification item 2 — specific and measurable]
- [Final outcome achieved]
After finishing, verify:
- [Verification item 1 — specific and measurable]
- [Verification item 2 — specific and measurable]
- [Final outcome achieved]
7. Common Problems and Fixes
7. Common Problems and Fixes
| Problem | Why It Happens | How to Fix |
|---|---|---|
| [Specific problem] | [Root cause] | [Clear solution] |
| [Specific problem] | [Root cause] | [Clear solution] |
| Problem | Why It Happens | How to Fix |
|---|---|---|
| [Specific problem] | [Root cause] | [Clear solution] |
| [Specific problem] | [Root cause] | [Clear solution] |
8. Notes
8. Notes
Assumptions made:
- [List any assumptions about user knowledge, tools, or environment]
Who to ask for help: [Role or person]
Assumptions made:
- [List any assumptions about user knowledge, tools, or environment]
Who to ask for help: [Role or person]
9. Version History
9. Version History
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | [Date] | [Author] | Initial version |
---| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | [Date] | [Author] | Initial version |
---Quality Checklist (Self-Verification)
质量检查表（自我验证）
Before finalizing output, verify ALL of the following:
在确定最终输出前，需验证以下所有内容：
Pre-Execution Check
执行前检查
- I checked for FOUNDER_CONTEXT.md and applied business context if available
- I asked clarifying questions only for genuinely missing information
- I asked 5 or fewer questions total
- 已检查FOUNDER_CONTEXT.md文件，若存在则已应用业务上下文
- 仅针对确实缺失的信息提出了澄清问题
- 总提问数不超过5个
Content Check
内容检查
- Process title is clear and specific
- Purpose statement is one clear sentence
- All tools and access requirements are listed
- Prerequisites are explicit and checkable
- Every step starts with an action verb
- No step assumes hidden knowledge
- Expected results are included for critical steps
- Warnings are placed before risky actions
- 流程标题清晰明确
- 目的说明为清晰的单句
- 已列出所有工具和访问权限要求
- 前提条件明确且可检查
- 每个步骤均以动作动词开头
- 无步骤假设受众具备隐藏知识
- 关键步骤已包含预期结果
- 已在风险操作前添加警告
Writing Check
写作检查
- Language is at 5th-grade reading level
- Sentences are short (10-15 words)
- No jargon without explanation
- Each step contains one action only
- Steps are in correct sequential order
- 语言难度为5年级阅读水平
- 句子简短（10-15个单词）
- 无未解释的行话
- 每个步骤仅包含一个动作
- 步骤顺序正确
Output Check
输出检查
- Quality checks are specific and measurable
- Common problems section includes likely issues
- Success state is explicitly defined
- The SOP can be followed without additional context
- Version info is complete
If ANY check fails → revise before presenting.
- 质量检查明确且可衡量
- 常见问题板块包含可能出现的问题
- 成功状态已明确定义
- 无需额外上下文即可遵循此SOP
- 版本信息完整
若任何一项检查未通过 → 修订后再呈现。
Defaults & Assumptions
默认设置与假设
Use these unless the user specifies otherwise:
- Audience: Beginner with no prior knowledge of this specific process
- Reading level: 5th grade (simple words, short sentences)
- Version: 1.0
- Author: From FOUNDER_CONTEXT.md if available, otherwise "Process Owner"
- Last Updated: Current date
- Process type: Repeatable business process (not one-time task)
- Completion time: Not specified unless mentioned
- Permissions: Standard user access unless specified otherwise
Document all assumptions made in the Notes section of the SOP.
除非用户另有说明，否则使用以下默认设置：
- 受众： 对该特定流程无前置知识的初学者
- 阅读水平： 5年级（用词简单、句子简短）
- 版本： 1.0
- 作者： 若FOUNDER_CONTEXT.md存在则取自该文件，否则为“流程负责人”
- 最后更新日期： 当前日期
- 流程类型： 可重复执行的业务流程（非一次性任务）
- 完成时间： 除非提及，否则不指定
- 权限： 除非另有说明，否则为标准用户访问权限
所有做出的假设均需记录在SOP的备注板块中。