Creates detailed Standard Operating Procedures (SOPs) for business processes. Use when user needs SOPs, process documentation, operational guides, workflow documentation, or step-by-step instructions for repeatable business processes.
Transform unstructured process descriptions into clear, actionable Standard Operating Procedures written at a 5th-grade reading level.
Check $ARGUMENTS first to determine execution mode:
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.
Proceed immediately to Task Execution (skip the "loaded" message).
When process description is available (either from initial $ARGUMENTS or follow-up message):
Check if FOUNDER_CONTEXT.md exists in the project root.
From the user's initial description, extract what's available:
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:
Using the information gathered, create a complete SOP following the structure in Output Format:
Hard constraints. No interpretation.
The SOP follows this exact structure:
# SOP: [Process Name]
**Version:** 1.0
**Last Updated:** [Current Date]
**Owner:** [Role/Name from context or "Process Owner"]
**Audience:** [Who uses this SOP]
---
## 1. Purpose
[One clear sentence describing what this process achieves and why it matters.]
## 2. Who Does This
[Role or skill level of person performing this process]
## 3. Tools You Need
- [Tool 1]
- [Tool 2]
- [Access/permissions required]
## 4. Starting Requirements
Before you start, make sure:
- [ ] [Requirement 1]
- [ ] [Requirement 2]
- [ ] [Everything you need is ready]
## 5. Step-by-Step Instructions
### Step 1: [Action Title]
1. [Do this specific action]
2. [Do this specific action]
**What you should see:** [Expected result or outcome]
### Step 2: [Action Title]
1. [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]
1. [Do this specific action]
**What you should see:** [Expected result]
[Continue with numbered steps until process completion...]
## 6. Quality Check
After finishing, verify:
- [ ] [Verification item 1 — specific and measurable]
- [ ] [Verification item 2 — specific and measurable]
- [ ] [Final outcome achieved]
## 7. Common Problems and Fixes
| Problem | Why It Happens | How to Fix |
|---------|---------------|------------|
| [Specific problem] | [Root cause] | [Clear solution] |
| [Specific problem] | [Root cause] | [Clear solution] |
## 8. Notes
**Assumptions made:**
- [List any assumptions about user knowledge, tools, or environment]
**Who to ask for help:** [Role or person]
## 9. Version History
| Version | Date | Author | Changes |
|---------|------|--------|---------|
| 1.0 | [Date] | [Author] | Initial version |
Before finalizing output, verify ALL of the following:
If ANY check fails → revise before presenting.
Use these unless the user specifies otherwise:
Document all assumptions made in the Notes section of the SOP.