QA Debugging

Use systematic debugging to turn symptoms into evidence, then into a verified fix with a regression test and prevention plan.

Default stance:

• Keep debugging evidence-first: reproduce, isolate, measure, then change one variable at a time.
• Treat logs, metrics, traces, and profiles as the default production debugging substrate.
• When telemetry implementation is missing or broken, hand off setup work to ../qa-observability/SKILL.md.
• For agentic systems, debug the full chain: user input, prompt/version, retrieval context, tool calls, model output, and guardrails.

Quick Reference