From scientific-method
Enforces scientific method—observation, falsifiable hypotheses, predictions, experiments, conclusions—for debugging unclear causes, intermittent issues, failed attempts, or uncertain architecture decisions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/scientific-method:scientific-thinkingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Enforces the scientific method as an investigation discipline. Governs hypothesis formulation,
Enforces the scientific method as an investigation discipline. Governs hypothesis formulation, predictions, experiment design, and evidence-based conclusions.
Load these references at the start of any investigation. A references index is available for a quick map of all shared files.
evidence-first-debugging handles observation recording, evidence IDs, and causality
validation. Both skills use the same Unified Investigation Template output structure. Load
evidence-first-debugging when the task requires structured evidence tracking alongside
hypothesis work.
Activate this skill when the prompt contains:
Apply this skill to problems with genuine uncertainty — unknowns, failed attempts, complex architecture trade-offs.
Tasks outside scope: typo fixes, simple additions, tasks with explicit step-by-step instructions already provided. For those, execute directly.
Enforce stages in this order. Each stage gates the next.
flowchart TD
S0[Stage 0-3: Observation<br>Record ONLY factual observations<br>No interpretation] --> S4
S4[Stage 4: Hypothesis Formulation<br>State H0 null and H1 alternative<br>Both must be falsifiable] --> S5
S5[Stage 5: Prediction<br>Write: If H1 is true, we should observe...] --> S6
S6[Stage 6-7: Experiment Design<br>Define Path A and Path B<br>Identify confounds] --> S8
S8[Stage 8-9: Execute<br>Run experiments<br>Record results verbatim] --> S10
S10[Stage 10-11: Conclusion<br>Classify causality<br>State decision<br>Cite evidence IDs] --> Done
Done{status?}
Done -->|resolved-verified| Retro[Notify user: retrospective-analyst<br>agent can produce mermaid timeline<br>and retrospective from iteration log]
Done -->|unresolved or mitigated| S0
Observation (sections 0-3):
evidence-first-debugging)Hypothesis Formulation (section 4):
Prediction (section 5):
Experiment Design (sections 6-7):
Execute (sections 8-9):
Conclusion (sections 10-11):
causal-supported, correlated-only, unrelated, or unknownnpx claudepluginhub jamie-bitflight/claude_skills --plugin scientific-methodProvides structured reasoning for stalled debugging or complex problems: frame issues, track hypotheses, gather/evaluate evidence, progress confidence levels to avoid loops.
Scientific bug hunting using falsifiable hypotheses. Forms hypotheses, designs falsifying tests, eliminates candidates systematically, and logs the full investigation trail in a structured debug/ folder. TRIGGER when: user has a bug to investigate scientifically; user wants systematic root-cause analysis; user says "debug", "investigate", "root cause", "why is this failing"; user invokes /autoresearch:debug. DO NOT TRIGGER when: user wants to optimize a metric (use /autoresearch); user wants to fix a known error automatically (use /autoresearch:fix); user just wants a quick one-line answer about what a function does.
Runs safe-to-fail probes for complex domain hypotheses: qualifies constraints/criteria in foreground, then background experiments to sense retrospective cause-effect. Triggers on 'probe', 'test hypothesis'.