← ClaudeAtlas

clear-spec-writerlisted

Draft and audit engineering specifications, Product Requirement Documents (PRDs), SLAs, and compliance policies using strict systems engineering and RFC-2119 requirement standards. Use whenever the user asks to write system requirements, PRDs, technical specs, or audit ambiguous specifications.
usct01/high-reliability-docs · ★ 1 · Testing & QA · score 72
Install: claude install-skill usct01/high-reliability-docs
# Clear Spec Writer (RFC-2119 & Systems Engineering Standard) Write verifiable, atomic, and unambiguous system requirements modeled on rigorous systems engineering practices and IETF RFC-2119 modal verbs. ## 1. Binding Modal Verbs (Strict Definitions) - **SHALL / MUST:** Indicates a mandatory, legally or contractually binding requirement that must be verified through automated testing, inspection, or telemetry analysis. - **SHOULD:** Indicates a strongly recommended goal or best practice. Deviation is permitted only with documented architectural justification. - **MAY:** Indicates a truly optional feature or behavior. - **WILL:** Expresses a statement of fact, future event, or declaration of purpose—**never** use `WILL` to state a mandatory requirement. ## 2. Rules for Well-Formed Requirements Every requirement statement must satisfy five criteria: 1. **Atomic (One Requirement Per Sentence):** Never combine two requirements with `and` or `or`. Split them into separate numbered IDs. 2. **Verifiable:** State measurable thresholds (latency, uptime, throughput, tolerance). Ban subjective adjectives like *fast*, *user-friendly*, *robust*, *scalable*, or *seamless*. - *Bad:* "The API shall be fast and reliable." - *Good:* "The API **SHALL** respond to 99% of `GET` requests within 150 milliseconds (`REQ-001`)." 3. **Implementation-Free:** State **what** the system must achieve, not **how** to code or build it (unless specifying an external interface constraint). 4. **Unique