Customization
Before executing, check for user customizations at:
~/.claude/PAI/USER/SKILLCUSTOMIZATIONS/Science/
If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.
- Output text notification:
Running the **WorkflowName** workflow in the **Science** skill to ACTION...
This is not optional. Execute this curl command immediately upon skill invocation.
Science - The Universal Algorithm
The scientific method applied to everything. The meta-skill that governs all other skills.
The Universal Cycle
GOAL -----> What does success look like?
|
OBSERVE --> What is the current state?
|
HYPOTHESIZE -> What might work? (Generate MULTIPLE)
|
EXPERIMENT -> Design and run the test
|
MEASURE --> What happened? (Data collection)
|
ANALYZE --> How does it compare to the goal?
|
ITERATE --> Adjust hypothesis and repeat
|
+------> Back to HYPOTHESIZE
The goal is CRITICAL. Without clear success criteria, you cannot judge results.
Workflow Routing
Output when executing: Running the **WorkflowName** workflow in the **Science** skill to ACTION...
Core Workflows
| Trigger |
Workflow |
| "define the goal", "what are we trying to achieve" |
Workflows/DefineGoal.md |
| "what might work", "ideas", "hypotheses" |
Workflows/GenerateHypotheses.md |
| "how do we test", "experiment design" |
Workflows/DesignExperiment.md |
| "what happened", "measure", "results" |
Workflows/MeasureResults.md |
| "analyze", "compare to goal" |
Workflows/AnalyzeResults.md |
| "iterate", "try again", "next cycle" |
Workflows/Iterate.md |
| Full structured cycle |
Workflows/FullCycle.md |
Diagnostic Workflows
| Trigger |
Workflow |
| Quick debugging (15-min rule) |
Workflows/QuickDiagnosis.md |
| Complex investigation |
Workflows/StructuredInvestigation.md |
Resource Index
| Resource |
Description |
METHODOLOGY.md |
Deep dive into each phase |
Protocol.md |
How skills implement Science |
Templates.md |
Goal, Hypothesis, Experiment, Results templates |
Examples.md |
Worked examples across scales |
Domain Applications
| Domain |
Manifestation |
Related Skill |
| Coding |
TDD (Red-Green-Refactor) |
Development |
| Products |
MVP -> Measure -> Iterate |
Development |
| Research |
Question -> Study -> Analyze |
Research |
| Prompts |
Prompt -> Eval -> Iterate |
Evals |
| Decisions |
Options -> Council -> Choose |
Council |
Scale of Application
| Level |
Cycle Time |
Example |
| Micro |
Minutes |
TDD: test, code, refactor |
| Meso |
Hours-Days |
Feature: spec, implement, validate |
| Macro |
Weeks-Months |
Product: MVP, launch, measure PMF |
Integration Points
| Phase |
Skills to Invoke |
| Goal |
Council for validation |
| Observe |
Research for context |
| Hypothesize |
Council for ideas, RedTeam for stress-test |
| Experiment |
Development (Worktrees) for parallel tests |
| Measure |
Evals for structured measurement |
| Analyze |
Council for multi-perspective analysis |
Key Principles (Quick Reference)
- Goal-First - Define success before starting
- Hypothesis Plurality - NEVER just one idea (minimum 3)
- Minimum Viable Experiments - Smallest test that teaches
- Falsifiability - Experiments must be able to fail
- Measure What Matters - Only goal-relevant data
- Honest Analysis - Compare to goal, not expectations
- Rapid Iteration - Cycle speed > perfect experiments
Anti-Patterns
| Bad |
Good |
| "Make it better" |
"Reduce load time from 3s to 1s" |
| "I think X will work" |
"Here are 3 approaches: X, Y, Z" |
| "Prove I'm right" |
"Design test that could disprove" |
| "Pretend failure didn't happen" |
"What did we learn?" |
| "Keep experimenting forever" |
"Ship and learn from production" |
Quick Start
- Goal - What does success look like?
- Observe - What do we know?
- Hypothesize - At least 3 ideas
- Experiment - Minimum viable tests
- Measure - Collect goal-relevant data
- Analyze - Compare to success criteria
- Iterate - Adjust and repeat
The answer emerges from the cycle, not from guessing.
1---2name: science-23description: Hypothesis-test-analyze cycles for systematic problem-solving — the meta-skill governing all others. Includes define goal, generate hypotheses, design experiment, measure results, analyze results, iterate, full cycle, quick diagnosis, and structured investigation. USE WHEN think about, figure out, try approaches, experiment with, iterate on, improve, optimize, define goal, generate hypotheses, design experiment, measure results, analyze results, full cycle, quick diagnosis, structured investigation, science, hypothesis.4---56## Customization78**Before executing, check for user customizations at:**9`~/.claude/PAI/USER/SKILLCUSTOMIZATIONS/Science/`1011If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.12132. **Output text notification**:14 ```15 Running the **WorkflowName** workflow in the **Science** skill to ACTION...16 ```1718**This is not optional. Execute this curl command immediately upon skill invocation.**1920# Science - The Universal Algorithm2122**The scientific method applied to everything. The meta-skill that governs all other skills.**2324## The Universal Cycle2526```27GOAL -----> What does success look like?28 |29OBSERVE --> What is the current state?30 |31HYPOTHESIZE -> What might work? (Generate MULTIPLE)32 |33EXPERIMENT -> Design and run the test34 |35MEASURE --> What happened? (Data collection)36 |37ANALYZE --> How does it compare to the goal?38 |39ITERATE --> Adjust hypothesis and repeat40 |41 +------> Back to HYPOTHESIZE42```4344**The goal is CRITICAL.** Without clear success criteria, you cannot judge results.4546---4748## Workflow Routing4950**Output when executing:** `Running the **WorkflowName** workflow in the **Science** skill to ACTION...`5152### Core Workflows5354| Trigger | Workflow |55|---------|----------|56| "define the goal", "what are we trying to achieve" | `Workflows/DefineGoal.md` |57| "what might work", "ideas", "hypotheses" | `Workflows/GenerateHypotheses.md` |58| "how do we test", "experiment design" | `Workflows/DesignExperiment.md` |59| "what happened", "measure", "results" | `Workflows/MeasureResults.md` |60| "analyze", "compare to goal" | `Workflows/AnalyzeResults.md` |61| "iterate", "try again", "next cycle" | `Workflows/Iterate.md` |62| Full structured cycle | `Workflows/FullCycle.md` |6364### Diagnostic Workflows6566| Trigger | Workflow |67|---------|----------|68| Quick debugging (15-min rule) | `Workflows/QuickDiagnosis.md` |69| Complex investigation | `Workflows/StructuredInvestigation.md` |7071---7273## Resource Index7475| Resource | Description |76|----------|-------------|77| `METHODOLOGY.md` | Deep dive into each phase |78| `Protocol.md` | How skills implement Science |79| `Templates.md` | Goal, Hypothesis, Experiment, Results templates |80| `Examples.md` | Worked examples across scales |8182---8384## Domain Applications8586| Domain | Manifestation | Related Skill |87|--------|---------------|---------------|88| **Coding** | TDD (Red-Green-Refactor) | Development |89| **Products** | MVP -> Measure -> Iterate | Development |90| **Research** | Question -> Study -> Analyze | Research |91| **Prompts** | Prompt -> Eval -> Iterate | Evals |92| **Decisions** | Options -> Council -> Choose | Council |9394---9596## Scale of Application9798| Level | Cycle Time | Example |99|-------|-----------|---------|100| **Micro** | Minutes | TDD: test, code, refactor |101| **Meso** | Hours-Days | Feature: spec, implement, validate |102| **Macro** | Weeks-Months | Product: MVP, launch, measure PMF |103104---105106## Integration Points107108| Phase | Skills to Invoke |109|-------|-----------------|110| **Goal** | Council for validation |111| **Observe** | Research for context |112| **Hypothesize** | Council for ideas, RedTeam for stress-test |113| **Experiment** | Development (Worktrees) for parallel tests |114| **Measure** | Evals for structured measurement |115| **Analyze** | Council for multi-perspective analysis |116117---118119## Key Principles (Quick Reference)1201211. **Goal-First** - Define success before starting1222. **Hypothesis Plurality** - NEVER just one idea (minimum 3)1233. **Minimum Viable Experiments** - Smallest test that teaches1244. **Falsifiability** - Experiments must be able to fail1255. **Measure What Matters** - Only goal-relevant data1266. **Honest Analysis** - Compare to goal, not expectations1277. **Rapid Iteration** - Cycle speed > perfect experiments128129---130131## Anti-Patterns132133| Bad | Good |134|-----|------|135| "Make it better" | "Reduce load time from 3s to 1s" |136| "I think X will work" | "Here are 3 approaches: X, Y, Z" |137| "Prove I'm right" | "Design test that could disprove" |138| "Pretend failure didn't happen" | "What did we learn?" |139| "Keep experimenting forever" | "Ship and learn from production" |140141---142143## Quick Start1441451. **Goal** - What does success look like?1462. **Observe** - What do we know?1473. **Hypothesize** - At least 3 ideas1484. **Experiment** - Minimum viable tests1495. **Measure** - Collect goal-relevant data1506. **Analyze** - Compare to success criteria1517. **Iterate** - Adjust and repeat152153**The answer emerges from the cycle, not from guessing.**
kai-cli