doc-verifierlisted

# Documentation Verifier This skill guides agents performing documentation verification for cloud infrastructure. Documentation drift -- the gap between what docs say and what the system does -- is the primary failure mode for operations manuals. The doc-verifier detects drift using NASA's TAID (Test, Analysis, Inspection, Demonstration) verification methods applied to documentation artifacts. Documentation drift is insidious because it compounds silently. A single undetected drift item erodes operator trust. Once operators stop trusting documentation, they stop reading it and start improvising. The doc-verifier breaks this cycle by making verification systematic and repeatable. ## Drift Detection Methods Four categories of documentation drift exist, each with distinct detection strategies. ### Configuration Drift **Definition:** Document says setting `X=A` but the running system has `X=B`. **Detection strategy:** 1. Parse documented configuration values from procedures (grep for `=`, `:`, or YAML key-value patterns) 2. Read actual configuration files (`/etc/kolla/*/` for Kolla-Ansible deployments, `globals.yml`) 3. Query API for runtime configuration where available (`openstack configuration show`) 4. Compare documented values against actual values 5. Flag mismatches with severity based on operational impact **Common sources:** Kolla-Ansible `globals.yml` changes, service reconfiguration, security hardening, upgrades. **Detection patterns:** - `OPS-KEYSTONE-*`: Comp