What problem does it solve? Debugging failures in the EVA platform often leads to guesswork, overly broad fixes, or changes that bypass safety mechanisms like the Approval Engine. This Skill enforces a disciplined process that reproduces the failure, isolates the root cause, and proves the fix with tests. ## Core Features & Use Cases - Structured Debugging Process: Follows a six-step workflow from reading the exact error to running focused and broader verification tests. - EVA-Specific Safety Checks: Verifies tenant boundaries, RLS and auth behavior, task state machine integrity, and Approval Engine compliance during debugging. - Runtime Safety Policy: Requires explicit approval before debugging production systems, tenant data, secrets, or destructive state. - Use Case: A NestJS service test fails after a migration. Use this Skill to reproduce the failure with the smallest command, identify the root cause in the data access layer, write a failing test, apply a minimal fix, and confirm tenant isolation is preserved. ## Quick Start Use the systematic-debugging skill to investigate this failing test, find the root cause, and fix it with a verified minimal change.
