gap-scannerlisted

# Gap Scanner Find where AZIMUTH's stated coverage exceeds its actual reference support, and where reference material covers domains not yet claimed. This skill reads files and produces a structured gap report. It does not propose fixes — it maps the delta between claims and reality. --- ## Protocol Run all 6 steps sequentially. Read each file group before drawing conclusions. --- ### Step 1 — Extract Coverage Claims from SKILL.md Read `SKILL.md`. Extract and list: 1. Every decision type in "Use When" 2. Every domain named in the DEEP mode load rules (tech/engineering → `software-failure-patterns.md`, product/launch → `launch-risks.md`, startup/venture → `startup-failures.md`) 3. Every diagnostic load condition (which module trigger → which diagnostic file) 4. Every domain-policy route (which Layer-3 domain → which file in `domain-policies/`) 5. Every domain explicitly named in the base rate load rule --- ### Step 2 — Audit Reference Files Against Claims For each domain claimed in Step 1, read the corresponding reference file. Assess coverage depth: - **STRONG**: File provides specific patterns, mechanisms, and diagnostic questions for this domain - **PARTIAL**: File mentions the domain but coverage is thin, hedged, or missing mechanisms - **THIN**: Domain is in base-rates.md but has no corresponding pattern file - **MISSING**: Domain is claimed in SKILL.md but no reference material exists for it Known gaps to confirm (from prior analysis): - **M&A / Partnership