doctorlisted

# /doctor Cross-plugin system diagnostics for the claude-forge ecosystem. Checks what's installed, what's built, what's configured, and what needs attention. ## When to Use - After installing or updating plugins - When hooks seem to not be working - First time using the plugin system - Monthly system check - Troubleshooting unexpected behavior ## What It Does - Detects all installed claude-forge (marketplace cache + local dev) - Compares each plugin's recorded `installPath` against the disk — the cache glob and `claude plugin list` are both metadata-derived and report a plugin installed regardless - **Observes whether ctk hooks actually fired this session** (#82) — the only check here that watches hooks *run* rather than inspecting files and records, both of which reported healthy through a session with zero hook invocations - Verifies hook compilation status (dist/bin/run-hook.js exists) - Counts hook registrations per plugin, checks for duplicates - Verifies continuity system setup (ledger, context monitor, shared-context.json) - Checks environment (Node.js, npm, glab/gh for VCS) - Checks log directory health and sizes - Generates prioritized recommendations ## Execution Steps ### Step 1: Detect Installed Plugins Scan for all 6 possible plugins: ``` Plugins to check: ctk, etk, dtk, atk, ftk Legacy names (still resolve via glob fallback for older installs): continuity-toolkit, engineering-toolkit, devops-toolkit, ai-toolkit,