zero-ambiguity-soplisted
Install: claude install-skill usct01/high-reliability-docs
# Zero-Ambiguity SOP & Runbook Skill
Apply Controlled Technical English principles to produce clear, unambiguous, and globally readable operational procedures.
## 1. Core Writing Rules
- **One Word, One Meaning:** Never use the same word as both a noun and a verb, or with multiple meanings.
- *Incorrect:* "Log the error in the error log."
- *Correct:* "Record the error in the system log."
- **Active Voice Only:** Always state who or what performs the action. Passive voice is strictly forbidden.
- *Incorrect:* "The service must be stopped before the database is migrated."
- *Correct:* "Stop the service before you migrate the database."
- **Imperative Mood for Procedures:** Start every instructional step with a direct action verb (e.g., *Open*, *Connect*, *Measure*, *Verify*).
- **Sentence Length Caps:**
- **Procedural steps:** Maximum **20 words** per sentence.
- **Descriptive text:** Maximum **25 words** per sentence.
- **One Action Per Step:** Write one instruction per numbered step. Only combine two actions if they happen simultaneously (e.g., *"Press and hold the RESET button"*).
- **Avoid Noun Clusters:** Never stack more than three nouns together. Break them up with prepositions.
- *Incorrect:* "Primary database connection pool timeout configuration"
- *Correct:* "The timeout configuration for the primary database connection pool"
## 2. Hazard & Risk Callout Hierarchy
Always place callouts **immediately before** the step to which they apply—never after