diagnose

# Diagnose Most failures in an aigent-OS install aren't bugs in any single component — they're integration failures across layers. `/diagnose` walks the stack with you so you don't have to. ## When to use - "It used to work, now it doesn't" - Caddy isn't surfacing a skill you expect - `/open` produces incomplete context - Hooks not firing - Wikilinks not resolving - AI behavior changed unexpectedly after an update - Anything you can't immediately attribute to a single component ## How to execute ### Step 1 — Capture the symptom Ask the user (or read from their prompt): - **What were you trying to do?** - **What happened instead?** - **What did you expect?** - **What changed recently?** (git pull, new skill installed, hook edit, kernel update) Frame the symptom in one sentence. Example: *"Caddy used to surface /channel-audit when I asked about YouTube performance, now it doesn't."* ### Step 2 — Walk the seven-layer stack For each layer, ask: could this layer be responsible for the symptom? If yes, run the specific check. If no, move on. ``` LAYER 7 — Principal Configuration - system/00_identity.md customized? - system/14_decision_framework.md reflects current priorities? - vault/projects/ and vault/people/ populated? Check first if symptom involves AI giving wrong context or missing your situation. LAYER 6 — Doctrine (vault/concepts/) - Has a relevant doctrine note been edited recently? - Are there standing rules that should be firing but aren't? ...