← ClaudeAtlas

thinking-scientific-methodlisted

Hypothesis → Prediction → Test → Revise with explicit falsification. Use for debugging, feature experimentation, performance investigation, and A/B testing design.
babypochi06/cc-thinking-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill babypochi06/cc-thinking-skills
# Scientific Method ## Overview The scientific method is a systematic approach to understanding through observation, hypothesis formation, prediction, testing, and revision. In engineering, it provides rigor to debugging, experimentation, and investigation. The key insight: good hypotheses must be falsifiable—you must be able to prove them wrong. **Core Principle:** Form hypotheses that could be proven false. Design experiments that could falsify them. Update beliefs based on evidence. ## When to Use - Debugging (systematic cause identification) - Performance investigation - A/B test design - Feature experimentation - Root cause analysis - Data analysis - Any investigation where you're testing theories Decision flow: ``` Investigating something? → Do you have a clear hypothesis? → no → FORM A HYPOTHESIS → Can your hypothesis be proven false? → no → MAKE IT FALSIFIABLE → Have you designed a test? → no → DESIGN AN EXPERIMENT → Did you update beliefs based on results? → no → REVISE AND ITERATE ``` ## The Scientific Method Process ### Step 1: Observe Gather data about the phenomenon: ```markdown ## Observation What I'm seeing: - API latency increased from 200ms to 800ms - Started approximately Monday 9 AM - Affects /checkout endpoint - Other endpoints are normal - Error rate is normal Initial data: - P50: 400ms (was 150ms) - P99: 2.5s (was 500ms) - Traffic: Normal levels ``` ### Step 2: Question What do you want to understand? ```markdown ## Question Cent