sop-authoring

# SOP Authoring

Effective Standard Operating Procedures (SOPs) transform complex workflows into reusable, deterministic instructions for AI agents. This skill covers the principles and practices for writing clear, actionable SOPs.

## Key Concepts

### What Makes a Good SOP

1. **Single Responsibility**: Each SOP addresses one specific workflow or task
2. **Deterministic**: Same inputs produce same outputs
3. **Actionable**: Every step is concrete and executable
4. **Parameterized**: Variables enable reuse across contexts
5. **Self-Contained**: Minimal external dependencies

### SOP vs. General Documentation

- **SOPs**: Prescriptive workflows with specific steps
- **Documentation**: Descriptive reference material
- **Guides**: Educational content with explanations
- **Tutorials**: Step-by-step learning experiences

Use SOPs when you need consistent, repeatable execution of multi-step processes.

## Best Practices

### Writing Clear Instructions

**DO:**

- Use active voice and imperative mood
- Start steps with action verbs (analyze, generate, validate)
- Be specific about expected outcomes
- Include success criteria for each step
- Use numbered lists for sequential steps
- Use bullet points for unordered items

**DON'T:**

- Use passive voice ("should be done" → "do this")
- Include vague instructions ("improve the code")
- Mix procedural and reference content
- Assume implicit knowledge without stating it

### Title and Description

```markdown
# {Action Verb} {Outcome} SOP

## Overview
{1-2 sentences describing what this SOP accomplishes and when to use it}
```

**Good Titles:**

- "Generate Codebase Documentation"
- "Implement Feature Using TDD"
- "Review Pull Request for Security"

**Poor Titles:**

- "Documentation" (too vague)
- "How to Maybe Improve Code Quality" (uncertain)
- "The Complete Guide to Everything" (too broad)

### Structuring Steps

**Sequential Steps:**

```markdown
## Steps

1. Analyze the codebase structure
   - Identify main entry points