Standard operating procedure

1---
2name: "sop"
3title: "Standard operating procedure"
4description: "Turns a verbal walkthrough or rough notes into a numbered SOP."
5audience: "internal"
6format: "structured-doc"
7tone: "direct"
8triggers:
9  - "write an SOP"
10  - "turn this into a procedure"
11  - "document this process"
12---
13
14## Overview
15This skill handles **Standard operating procedure**. It produces structured doc output in a direct voice, written for internal team.
16When this skill is triggered, expect the user to provide: **Verbal walkthrough, raw process notes, or checklist draft**. If this input has not been provided, ask for it before proceeding — do not guess or use placeholder data.
17## Process
181. State the purpose, owner, and when the procedure should be used.
192. Lay out the steps in exact execution order with clear action verbs.
203. Call out decision points or exceptions separately so operators do not miss them.
214. Finish with checks that confirm the procedure was completed correctly.
22## Quality Standards
23- Use headings the team already recognises
24- Assign an owner to every action item
25- Flag blockers or risks with clear impact statements
26- Keep it under 500 words unless complexity demands more
27
28## What to Avoid
29
30- Do not use ambiguous verbs or assume prior context the operator may not have.
31
32## Example Triggers
33- "write an SOP"
34- "turn this into a procedure"
35- "document this process"