SOP Writer Skill

Produces formal, audit-ready SOPs suitable for regulated industries, ISO certification, or operational scaling.

Required Inputs

• SOP title (e.g. "SOP-001: New Client Onboarding")
• Department / function
• Process description
• Regulatory or quality standard (ISO 9001, GMP, CQC, FCA, etc.)
• Roles involved
• Tools or equipment used

Output Structure

[COMPANY NAME] — Standard Operating Procedure

1. Purpose

[1-2 sentences. Why does this SOP exist?]

2. Scope

Applies to: [Roles, departments, locations] Does not apply to: [Explicit exclusions]

3. Definitions

4. Responsibilities

5. Required Materials / Tools / Access

• [Item]

6. Procedure

NOTE: Steps must be written in imperative form. Each step must have one action only.

7. Quality Checks

8. Non-Conformance

1. [Immediate action]
2. [Who to notify]
3. [How to document deviation]

9. References

[Related SOPs, policies, standards]

10. Document History

Quality Checks

• All steps written in imperative form ("Open...", "Navigate...", "Confirm...")
• Each step has exactly one action
• Role specified for every step
• Quality checkpoints at critical stages
• Non-conformance process defines who to notify and how to document
• Document history table and review date are included

Example Trigger Phrases

• "Write an SOP for [process]"
• "Create a standard operating procedure for [task]"
• "Write a work instruction for [process]"

Anti-Patterns

• Do not write steps that contain more than one action — each step must be a single, auditable action in imperative form
• Do not omit a role from any step — every action must be assigned to a specific role or the SOP cannot be enforced
• Do not skip the non-conformance section — an SOP without a deviation process cannot meet audit or regulatory requirements
• Do not produce an SOP without a review date and version history — undated documents cannot be relied upon for compliance
• Do not use passive voice in procedure steps — write "Open the system" not "The system should be opened"