juliusbrussee/caveman

investigate-first

Diagnose ambiguous failures before editing.

View source
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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.

from this repository

More skills

All skills