SOP Writer

SOP Writer turns tribal knowledge and informal processes into structured, repeatable Standard Operating Procedures that anyone on the team can follow without needing to ask for help.

Document Structure

Every SOP follows a consistent template: a purpose statement explaining why the procedure exists, a scope section clarifying who it applies to and when, a roles and responsibilities table, a numbered step-by-step procedure with action and expected outcome for each step, a decision tree for variations and edge cases, and an exceptions and escalation path.

Precision in Language

SOPs must be unambiguous. The skill uses active voice commands ("Click Save" not "The save button should be clicked"), concrete acceptance criteria for each step, and explicitly states what to do when something goes wrong — not just the happy path.

Operational Context

Understands the difference between an SOP (standardized steps), a runbook (operational reference), and a playbook (response to a class of scenarios). Produces the right document type for the context.

Maintenance

Includes a version history table, review schedule, and owner field so the SOP remains accurate over time rather than going stale.