debug-retro
Installation
SKILL.md
/debug-retro
Each time the human stepped in during a debug session, they supplied something the agent could have found alone. Count those steps and give each one a lasting home, so the next session needs fewer. The goal is zero steps per bug.
1. List the interventions
Read this conversation from the start of the debug session. An intervention is a human message that did one of these:
| Kind | The human… |
|---|---|
| control | gave a comparison case, or asked the agent to set one up |
| fact | supplied data, or pointed at data the agent had not gathered |
| constraint | pushed back with a fact that killed a hypothesis |
| proxy | ran a command, pasted output or a screenshot, or quoted a dashboard number the agent could have read itself |
| method | told the agent how to work: run the repro, cite, split the hypothesis, go a layer down |
| decision | picked a fix, or made a rollback, escalation or scope call |
The original bug report is not an intervention. Decisions are expected, so count them apart from the rest.