← ClaudeAtlas

high-reliability-docslisted

Orchestrate and combine high-reliability documentation standards across executive correspondence, operational action plans, zero-ambiguity SOPs, and verifiable engineering specifications. Use whenever drafting complex operational documents, technical directives, runbooks, incident playbooks, or policy memos that require strict structure and zero ambiguity.
usct01/high-reliability-docs · ★ 1 · Data & Documents · score 72
Install: claude install-skill usct01/high-reliability-docs
# High-Reliability Documentation Orchestrator Use this meta-skill to select, route, and combine specialized documentation standards into a single cohesive document. ## 1. The Container + Content Architecture Never apply two outer document layouts at once. Instead, pair one **Container Standard** (outer structure) with one or more **Content Standards** (inner writing rules): - **Container Standards (Choose ONE for outer layout):** 1. `executive-decision-memo`: Formal leadership decisions, policy directives, approvals, and official records. 2. `goal-action-plan`: Multi-team execution plans, incident response, product launches, and crisis management. 3. `clear-spec-writer`: Standalone engineering specifications, PRDs, and SLAs. 4. `zero-ambiguity-sop`: Standalone operator manuals, runbooks, and maintenance SOPs. - **Content Standards (Stack as needed inside sections):** - Use **`zero-ambiguity-sop` rules** inside any *How-To*, *Execution Step*, or *Runbook* section (20-word limit, active voice, imperative mood, `CRITICAL`/`CAUTION` callouts before steps). - Use **`clear-spec-writer` rules** inside any *Policy*, *Criteria*, *SLA*, or *Constraint* section (`SHALL`, `SHOULD`, `MAY`, measurable thresholds, unique IDs). - Use **`executive-decision-memo` BLUF rules** for all *Executive Summaries*, *Purpose* paragraphs, and *Leadership Intent* blocks. ## 2. Routing & Combination Matrix | User Request Type | Container Skill (Layout) | Content Skill(s) to Inject | How