What problem does it solve? Developers often jump straight to patching symptoms when a test fails or a bug appears, leading to wasted hours of guess-and-check fixes that never address the real cause. This Skill enforces a disciplined root-cause-first debugging workflow so fixes actually stick. ## Core Features & Use Cases - Four-Phase Process: Root cause investigation, pattern analysis, hypothesis testing, and verified implementation with a failing reproduction test. - Multi-Stack Tracing: Concrete guidance for tracing data flow across Flutter/Riverpod, FastAPI/Pydantic, Express/Prisma, Postgres, and FCM boundaries, including cross-repo request_id propagation. - Anti-Thrashing Guardrails: Red-flag detection and a hard stop after three failed fix attempts to force architectural re-evaluation. - Use Case: A FastAPI endpoint returns 422 in production. Instead of guessing, the Skill walks you through checking the Pydantic schema, router signature, and dependency order until the true cause is confirmed, then requires a failing test before the fix. ## Quick Start Use the systematic-debugging skill to investigate why my Prisma query returns empty results before suggesting any fix.
