Skill detail
investigate-first
Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.
Why we recommend it: Diagnoses ambiguous failures before editing: separates symptom from cause, traces state and boundaries, and ranks hypotheses by evidence and falsification value.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: investigate-first description: Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses. --- # Investigate first Gather evidence before changing product code. - Separate observed symptom from inferred cause. - Trace inputs, state transitions, ownership boundaries, and failure output. - Rank hypotheses by evidence and cheap falsification value. - Do not edit until one credible mechanism explains evidence. - Stop exploration when evidence is sufficient to name cause or exact blocker. Report cause and proof. Make no fix unless task authorizes implementation.Read the full source on GitHub (opens external page)