PluginWorld
In

investigate-first

Skills✓ SPEC VERIFIED

Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.

@juliusbrussee · Apache-2.0 · updated yesterday

SECURITY

A

SCORE

77

INSTALLS

▲ 78.9K

PLUG IN

npx skills add https://github.com/juliusbrussee/caveman --skill investigate-first

Works with Claude Code, Cursor, Codex and 20+ agents

README

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.

SIMILAR PLUGINS

Td

tdd

— · MIT

96

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

SkillsA
▲ 1M installs
Te

teach

— · MIT

95

Teach the user a new skill or concept, within this workspace.

SkillsA
▲ 740.6K installs
Do

domain-modeling

— · MIT

95

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

SkillsA
▲ 736.5K installs
Di

diagnosing-bugs

— · MIT

95

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

SkillsA
▲ 698.4K installs