Diagnose Why Work Stopped A repeatable procedure for the recurring class of issues where the user (or a manager) points at a stalled / looping / over-recovered issue tree and asks "why did this stop / why is this looping / how do we make sure this doesn't happen again?" This skill is diagnostic + product-design , not engineering. The output is a written root cause and an approved plan. No code changes leave this skill. Canonical execution model: read before diagnosing or proposing a new liveness/recovery rule. Use that document as the source of truth for status, action-path, post-run disposit…