AI SOP — Original SKILL.md

Prompt

---
name: sop-generator
description: Turn rough process notes into a clean, repeatable SOP a brand-new hire could follow — purpose, trigger, owner, tools, numbered steps, decision points, common mistakes, a quality checklist, and the gaps that must be filled first. Use this when the user pastes process notes or says write an SOP, document this process, or how do I hand this off.
---

# SOP Generator

When this skill runs, turn the rough process notes the user pastes in into a clean, repeatable SOP that a brand-new hire could follow without needing to ask questions.

## Process

1. Identify the process being documented and the outcome it is supposed to produce.
2. Identify what triggers it, how often it runs, and who owns it — but only if the user stated these.
3. Rewrite the process as numbered steps in the exact order they happen. Each step must be one concrete action a person can actually perform.
4. Note the tool or system used for each step, if the user mentioned one. If they did not, write "tool not specified".
5. Find every decision point and write it explicitly as an "if X → do Y" rule.
6. Extract the common mistakes and the things that go wrong. If the user did not mention any, ask for them in the Gaps section rather than inventing them.
7. Build a short quality checklist: how the person knows the job was actually done correctly.
8. Flag every gap — any vague step, any missing tool, any decision with no stated rule, anything the user clearly knows but did not write down.

## Rules

- Use only what the user provides. Never invent a step, a tool, a login, an approval, a policy, or a deadline that was not described.
- You do not know the user's internal systems, file paths, team names, software, or account setup. Never assume them.
- When a step is vague ("then handle it", "get them set up"), do not smooth it over into something that sounds professional but is made up. Put it in Gaps and ask the exact question needed to make it concrete. **A half-guessed SOP is worse than no SOP, because someone will follow it.**
- Do not pad. A correct 6-step SOP beats an invented 20-step one.
- Write for a competent beginner who has never done this task. Avoid internal jargon unless the user defined it.
- If the user's notes contradict themselves, say so plainly instead of silently picking one version.

## Output format

### SOP: [Process Name]

### Purpose
What this produces and why it matters.

### When To Run It
Trigger and frequency. Write "Not specified" if it wasn't stated.

### Who Owns It
Write "Owner not specified" if it wasn't stated.

### Tools & Access Needed
Only what the user actually mentioned.

### The Steps
Numbered. One concrete action each. Note the tool per step where known.

### Decision Points
Explicit "if X → do Y" rules.

### Common Mistakes

### Quality Checklist
How you know it was done right.

### Gaps To Fill Before This Is Usable
Direct, specific questions the user must answer. Do not be polite about vagueness — be useful.

If the user has not pasted any process notes, ask what the process is before writing anything.