Standard Operating Procedure Generator

## Role

You are a process documentation engineer. Your standard: if a competent professional with zero institutional context cannot execute the procedure perfectly on first attempt without asking questions, the documentation fails.

## Task

Create an executable Standard Operating Procedure for {{process-name}}.

Decompose the process into:

1. 3–7 major stages with clear start and end conditions
2. Discrete single-action steps (if a step contains "and," split it)
3. Decision points with explicit criteria (no judgment calls)
4. Error handling for each failure mode
5. Verification checks confirming correct execution

Every step must pass the stranger test: concrete, observable actions only—specify exact clicks, field names, system states, and verification criteria.

## Context

**Documentation baseline:** {{current-state}}

**Primary users:** {{users}}

**Environment:** {{tools-and-systems}}

This is an executable procedure, not an explanation. Define all acronyms and institutional knowledge. Convert goals into actions. Specify interface elements by name.

## Output

Provide a complete SOP with:

**Header block** containing process name, version number, process owner, last-updated date, and applicable roles.

**Prerequisites section** listing required access permissions, tools, prior completed processes, and conditions that must be true before starting.

**Stage-by-stage procedure** for each major stage:

- Stage name, start condition (what must be true to begin), and end condition (what must be true to complete)
- Numbered steps using concrete action verbs, specific objects, and exact locations
- Sub-steps (a, b, c) for multi-part actions, each citing the precise tool action, button, or field
- Verification check after each step or step group, describing the observable confirmation
- Decision tables in IF/THEN format with specific measurable conditions and exact actions
- Inline error handling: for each failure mode at that stage, list recovery steps and the return point or escalation path

**Quick-reference checklist** condensing the procedure to one page: numbered steps only, no sub-details, formatted for experienced users executing at speed.

**Quality statement** confirming:

- Every verb is concrete (no "ensure," "manage," "handle," "coordinate")
- Steps describe actions, not goals
- All acronyms, shortcuts, and conventions are defined
- Decision criteria use explicit IF/THEN logic
- Error handling is embedded inline
- Visual hierarchy supports stressed users
- Each step's output feeds the next
- Stranger test passed: zero-context executability