---
name: sop-guide-architect
description: "Drafts a complete SOP for a business process from scratch, with purpose, scope, owners, numbered steps, and optional checklists a new hire can follow unaided. Use when you need an SOP for a business process from scratch, such as invoice approval, with roles, numbered steps, and checklists. Do not use for cleaning up rough SOP notes you already have or building a staff training syllabus. Related topics: productivity, work, sop."
---

# SOP Guide Architect

Drafts a complete SOP for a business process from scratch, with purpose, scope, owners, numbered steps, and optional checklists a new hire can follow unaided.

## When to use

Use this skill when you need an SOP for a business process from scratch, such as invoice approval, with roles, numbered steps, and checklists. Do not use it for cleaning up rough SOP notes you already have or building a staff training syllabus.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Write a one-sentence purpose and a scope that states what the process covers and what it excludes.
3. List the responsible roles and what each one owns, using role names only.
4. Break the process into the requested number of steps, each starting with a verb and ending with its expected result or hand-off.
5. Attach each required document to the step where it is used and add per-step checklists if requested.
6. Add the run frequency and the trigger that starts the process, then confirm a newcomer could follow it unaided.

## Inputs

- **Process name** (free text, e.g. "Invoice approval")
- **Audience** (choose one: Front-line staff, Team leads, Managers, Executives)
- **Number of steps** (number from 3 to 20)
- **Include a checklist per step** (choose one: Yes, No)
- **Required documents** (choose any: Form A, Form B, Policy document, None)
- **How often it runs** (choose one: Daily, Weekly, Monthly, Quarterly, Annually)

## Output

A markdown SOP with title, purpose, scope, responsibilities, numbered steps, and a checklist table per step when requested.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### SOP Guide Architect

Draft a Standard Operating Procedure for a process I describe, written so someone who has never done it can follow it without asking questions.

- Process name: {{Process name}}
- Audience: {{Audience}}
- Number of steps: {{Number of steps}}
- Include a checklist per step: {{Include a checklist per step}}
- Required documents: {{Required documents}}
- How often it runs: {{How often it runs}}

Open with the purpose in one sentence and a scope that says what the SOP covers and what it leaves out. Name who is responsible for each part by role, not by person. Write the procedure as numbered steps that each start with a verb and contain one action, and put the expected result or hand-off at the end of each step so the reader knows it worked. Match the vocabulary and level of detail to the audience. Where a required document is used, say at which step. If checklists are requested, add a short table per step with the items to tick before moving on. Finish with the run frequency and any trigger that should start the process.

## Pitfalls

- Combining two actions in one step, which makes it impossible to tell where a failure happened.
- Naming individuals instead of roles, so the SOP goes stale the day someone changes jobs.
- Using vocabulary pitched above the audience, such as policy jargon in a front-line SOP.
