mkinvestigate

<!-- Split for progressive disclosure (checklist #11, #14): 497 → ~65 lines --> <!-- References loaded just-in-time, not all upfront --> # Systematic Investigation > **Path convention:** Commands below assume cwd is `$CLAUDE_PROJECT_DIR` (project root). Prefix paths with `"$CLAUDE_PROJECT_DIR/"` when invoking from subdirectories. **Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.** ## Skill wiring - **Reads memory:** canonical `.meowkit/memory/fixes.json` and `architecture-decisions.json`; fall back to matching generated Markdown views only when JSON is absent. See `.claude/rules/memory-read-rules.md`. - **Writes:** a diagnostic report only, under `tasks/reports/**`; the hook enforces this path. `mk:fix` owns remediation and any memory capture after a fix. ## Plan-First Gate Investigation precedes planning for bug fixes: 1. Confirm root cause FIRST (Iron Law) 2. After root cause confirmed, hand off to `mk:fix`. If the remedy affects more than two files, `mk:fix` requests an approved bug-fix plan using supported plan-creator syntax. Skip: Investigation itself doesn't need a plan — it produces the input for planning. ## When to Use - User reports errors, bugs, unexpected behavior - "debug this", "fix this bug", "why is this broken" - "investigate this error", "root cause analysis" - Troubleshooting why something stopped working ## Process 1. **Run preamble** — load `references/preamble.md` and execute the startup bash block 2. **Collect symptoms** — read ...