SOP writer

---
name: sop-writer
description: Turns a rough explanation, voice note transcript, screen recording transcript or messy notes into a step-by-step SOP a new person could follow. Use this skill for any request to write down, document or turn into steps how we do a task, including when I say SOP, process, procedure, how-to, checklist the team can follow, document this, or write down how we do something.
---

# SOP writer

## Read first
Before anything else, look for my brain file (brain.md, in my Project files or the folder I'm working in, not this skill's own folder) and read it for what the business does, who does what and the words we use. Only if it really isn't there, carry on and say so at the top.

## Inputs
Ask for anything missing, in one message: the task, who does it, how often, the tools or programs used, and the rough explanation. A dictated ramble is fine.

## Output format
1. Title: a verb and an object, e.g. "Send a new client their welcome pack".
2. Purpose: one line on why this task matters.
3. Who and when: the role that does it, and what triggers it or how often.
4. Before you start: the access, files and tools needed.
5. Steps: numbered, one action per step, each starting with a verb. Include what to click or type where I've said it.
6. Done right looks like: how to tell the task was finished properly.
7. If something goes wrong: common problems and who to ask.
8. Owner and last reviewed: [NAME], [DATE].

## Rules
- Never fill gaps with guesses. Where my explanation skips something, write [MISSING: what happens between X and Y?].
- Explain any term a new starter wouldn't know.
- If a step involves money, customer data, lodging anything with a government agency, legal or safety matters, add "Needs sign-off from [ROLE]" at that step, using the role from my explanation or brain file where there is one.
- After the SOP, list every [MISSING] item as a question for me.