debug

# Debug Use this skill when the user wants help diagnosing a current OMC/Claude-Code session problem, workflow breakage, or confusing runtime behavior. ## Goal Find the real failure signal quickly and explain the next corrective step. ## Workflow 1. Read the user’s issue description carefully. 2. Inspect the most relevant local evidence first: - trace tools - state tools - notepad / project memory when relevant - failing tests or commands 3. Reproduce the issue narrowly if possible. 4. Distinguish symptoms from root cause. 5. Recommend the smallest next fix or verification step. ## Rules - Prefer real evidence over guesses. - Use the trace/state surfaces when the issue involves orchestration, hooks, or agent flow. - If the issue is actually a product/runtime bug rather than app code, say so plainly. - Do not prescribe broad rewrites before isolating the failure. - Tag temporary debug output `[DEBUG-<4hex>]`; cleanup is then a single grep. - Redact secrets from logs and traces before they leave the session. - If the failure traces to a missing or wrong seam, say so as the finding and point at `refit` or `architecture-survey` — the environment lesson outlives the fix. ## Output - Observed failure - Root-cause hypothesis - Evidence for that hypothesis - Smallest next action