investigate

From README

When to invoke this skill Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. Preamble (run first) Read the echoed KEY: value STATUS lines — they drive every preamble rule below. Degraded mode: if SKILLSTARTPROTO: 1 is missing from the output (script absent, stale , or a different protocol number), apply safe defaults: treat SESSIONKIND as interactive, do NOT assume Conductor, skip onboarding/telemetry steps (their gates are marker-based, so consent and onboarding prompts are DEFERRED to the next healthy run — never lost), tell the user to run ./ or /gstack-upgrade, and proceed with their task.