← ClaudeAtlas

diagnose-firstlisted

Investigate a production symptom down to a named root cause BEFORE writing any fix. Use when: it does not get fixed, the same error keeps coming back, a previous fix did not change the observed behaviour, or you are about to jump on the first plausible cause. Do NOT use when: what you need is to re-read the product design.
RICK-ORPHEN/agent-discipline-skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill RICK-ORPHEN/agent-discipline-skills
# diagnose-first — pin down the scope before you fix ## Why this exists A report came in that a system "cannot produce minutes." **Six deploys, and the symptom did not change once.** Every round had a plausible cause and a cheap fix. | | What was fixed | Result | |---|---|---| | 1 | the recovery execution slot | still 400 | | 2 | the stalled-progress check | still 400 | | 3 | name/content matching | still 400 | | 4 | rebuilding the WAV | still 400 | | 5 | plan reuse | still 400 | | 6 | delivery and recording | (stopped to investigate) | On the sixth round the **audit log for other meetings** finally got looked at. One query. It showed: - Subject A (975 s / 69 chunks) — **34 chunks rejected by the provider**, the failures landing on index 2, 4, 6 … 68, every other one. The error text was different from the meeting being chased (`Audio file might be corrupted or unsupported`). And it had finished by **declaring "recovery complete" and producing minutes from half the audio** - Subject B (segment 4 of 72 missing) / Subject C (segment 2 of 175 missing) — segments never reached storage - Subject D — audio too short - Subject E — the single .wav that had been chased six times **There were four distinct faults, and one of them had been fixed six times.** The most damaging one was the one nobody was chasing. "It cannot produce minutes" is noticeable. "It produced minutes from half the audio" is not. This document is not a mindset. **It is a gate you pass before you star