← ClaudeAtlas

ops-manual-writerlisted

Guidance for writing OpenStack operations manual procedures following NASA document standards. Use when authoring per-service procedures, maintenance workflows, or operational documentation that must be verified against running infrastructure.
Tibsfox/gsd-skill-creator · ★ 61 · AI & Automation · score 80
Install: claude install-skill Tibsfox/gsd-skill-creator
# Operations Manual Writer This skill guides agents producing operations manual content for the GSD OpenStack Cloud Platform. Every procedure must follow NASA document standards adapted for cloud operations per SP-6105 SS 5.5 (Product Transition) and NPR 7123.1 Process 9 (Product Transition). The operations manual is the primary handoff artifact between the deployment crew and the operations crew. The goal is consistency and verifiability: every procedure an operator follows must be structured so that another agent (doc-verifier) can confirm the procedure matches the running system, and another operator can execute it without ambiguity. ## Procedure Format Template Every operational procedure follows the standard format derived from NASA-STD-3001 (adapted for cloud operations) as specified in the project reference document (Section 3.4 of gsd-openstack-nasa-reference.md): ``` PROCEDURE ID: OPS-{SERVICE}-{NUMBER} TITLE: {What this procedure accomplishes} SE PHASE: Phase E (Operations & Sustainment) NPR REFERENCE: NPR 7123.1 SS 3.2 Process 9 (Product Transition) LAST VERIFIED: {YYYY-MM-DD} against {OpenStack release version} VERIFIED BY: {doc-verifier agent / manual verification} PURPOSE {One to three sentences explaining why an operator would perform this procedure and when it should be executed.} PRECONDITIONS 1. {System state required before starting} 2. {Services that must be running} 3. {Access credentials or permissions needed} 4. {Backup state confirme