Investigate First
Diagnose ambiguous failures before editing.
by juliusbrussee · Apache-2.0
The skill
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.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: juliusbrussee/investigate-first-60803812181.
Details
- Publisher
- juliusbrussee
- Category
- Software Development › Misc
- License
- Apache-2.0
- Updated
- 2026-10-17
References
More from juliusbrussee
- Cavecrew When to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or…
- Caveman Compress Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens,…
- Caveman Stats Show recorded output and cache-read token usage and mode attribution for the current Claude Code…
- Caveman Terse caveman voice: answer first, fluff gone, every technical fact kept.