What problem does it solve?
This Skill prevents the AI from low-effort “giving up” behavior by enforcing an evidence-first, failure-mode-driven, high-pressure execution loop during complex development, debugging, review, and risky operations.
Core Features & Use Cases
- Failure-mode detection & forced method shift: identifies patterns like looping, blame-shifting, or “no-search guessing,” then switches to genuinely different investigation or implementation paths.
- PUA-DIAGNOSIS gate before action: when failures happen or validation is questioned, it outputs a structured diagnosis (problem + evidence + next action) to ensure every step generates new information.
- Pressure escalation with verification enforcement: increases intensity across L1–L4 escalation levels and requires concrete verification before claiming completion, especially after repeated failures.
Use case examples:
- You repeatedly hit the same bug and the AI keeps tweaking superficial parameters—use pua to force deeper evidence collection and alternate hypotheses.
- You’re close to “done” but no solid validation was run—use pua to require real commands/tests and a proof of correctness.
- A task is high-risk or spans multiple files—use pua to proactively assess boundaries without delegating verification back to the user.
Quick Start
Ask the AI to solve your failing task with strong evidence and verification, for example: “Use pua to diagnose the failure, switch methods if it’s looping, and run the required tests before declaring it fixed.”