Software Development
Diagnose
Use when the user reports misbehaving software to investigate — a bug, crash, wrong output, flaky behavior, or '為什麼壞掉/不會動/查一下' — and the root cause is not yet established. Enforces building a red-capable reproduction command BEFORE any hypothesis is allowed, then 3-5 ranked falsifiable hypotheses before testing any single one. NOT for conceptual questions, code reading requests, or feature work. When a failing command already exists, Step 1 is pre-satisfied — still apply, jumping straight to the hypothesis discipline.
- Publisher / source
- KerberosClaw/kc_ai_skills (found on the CSV list)
- Upstream record
- KerberosClaw/kc_ai_skills
- Version
- Version 2
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-03
- Content fingerprint
053c4a8eb26dd4e886e988340d0b677a8ac8798f5687569f3ffadf030711a241