evidence-based-debugginglisted

# evidence-based-debugging ## Purpose When an agent (or the lead) is debugging a failure, this skill constrains the work to **cite specific runtime evidence** — stack traces, log lines, variable snapshots, test output, timestamps — before proposing a fix. The failure mode this prevents: "patch and pray" — an agent proposes a plausible-looking fix based on the file structure without verifying that the proposed change addresses the actual runtime cause. Often passes review (looks reasonable) and ships to production where it doesn't fix anything because the real bug is elsewhere. Maps to [Syncause/debug-skill](https://github.com/Syncause/debug-skill) from awesome-harness-engineering's debugging category. ## Scope - Applies to any debugging task: failing test, production incident, customer-reported bug, "this used to work" regression - Output is a structured diagnosis + cited fix proposal - Does NOT apply to greenfield development (no runtime to cite) - Does NOT skip writing tests (the fix must come with a test that fails before the fix and passes after) ## Automated pass The agent doing the debugging MUST produce a written diagnosis following this template before proposing changes: ```markdown ## Diagnosis **Symptom observed:** <one line; cite where you saw it> **Evidence:** - <log line / stack trace / test output / etc.> Source: <file:line OR command:invocation OR ndjson:ts> - <next evidence item> Source: ... - <minimum 3 evidence items; cite each> **Hypothe