loom-debugging-and-error-recoverylisted

# loom-debugging-and-error-recovery Debugging is a recovery playbook. It preserves the failure, finds the root cause, fixes the scoped issue, guards against recurrence, and records what future work needs. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-evidence`, `loom-research`, `loom-tickets`, `loom-specs`, `loom-ralph`, `loom-audit`, `loom-retrospective`, and `loom-knowledge`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. ## Use This Playbook When Use this playbook when: - a test, build, type check, lint, CI, browser, or runtime command fails - a bug report arrives - behavior does not match spec, ticket acceptance, or operator expectation - a regression or intermittent failure needs localization - recovery needs a guard test, evidence, or follow-up ticket ## Route Use this route: ```text stop -> feedback loop -> preserve -> reproduce -> localize -> trace -> hypothesize -> instrument -> reduce -> fix -> guard -> verify -> prevent ``` ## Stop Pause feature expansion when unexpected failure appears. Do not pile unrelated changes on top of an unexplained failure. Update the active ticket if the failure changes scope, risk, or state. ## Feedback Loop Build the fastest reliable pass/fail loop you can before diagnosing deeply. Useful loops include: - focused failing test at the seam that reaches the bug - CLI or HTTP script with fixture