Skip to content
Skills Library
Science & research · Analysis

science

/science

Hypothesis-test-analyze cycles for systematic problem-solving — the meta-pattern underlying all the other thinking modes. 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.

Repository
ajbm-skills ↗
Licence
MIT
Last repository change
13.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
14
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Hypothesis-test-analyze cycles for systematic problem-solving — the meta-pattern underlying all the other thinking modes. 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.

Original author description

Hypothesis-test-analyze cycles for systematic problem-solving — the meta-pattern underlying all the other thinking modes. 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.

How it works

  1. The Universal Cycle
  2. Workflow Routing
  3. Resource Index
  4. Domain Applications
  5. Scale of Application
  6. Integration Points with Other Thinking Modes
  7. Key Principles (Quick Reference)
  8. Anti-Patterns
  9. Quick Start
Original SKILL.md headings · 134 lines, 605 words
SKILL.md preview
---
name: science
description: Hypothesis-test-analyze cycles for systematic problem-solving — the meta-pattern underlying all the other thinking modes. 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.
---

# Science — The Universal Cycle

**The scientific method applied to everything.** This is the meta-pattern underlying the other thinking modes.

## 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

### 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 the thinking modes implement Science |
| `Templates.md` | Goal, Hypothesis, Experiment, Results templates |
| `Examples.md` | Worked examples across scales |

---

## Domain Applications

| Domain | Manifestation |
|--------|---------------|
| **Coding** | TDD (Red-Green-Refactor) |
| **Products** | MVP → Measure → Iterate |
| **Research** | Question → Study → Analyze |
| **Prompts** | Prompt → Eval → Iterate |
| **Decisions** | Options → Council → Choose |

---

## 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 with Other Thinking Modes

| Phase | Modes to Invoke |
|-------|-----------------|
| **Goal** | Council for validation |
| **Observe** | Research for context |
| **Hypothesize** | Council for ideas, Red Team for stress-test |
| **Experiment** | Parallel worktrees for parallel tests |
| **Measure** | Evals for structured measurement |
| **Analyze** | Council for multi-perspective analysis |

---

## Key Principles (Quick Reference)

1. **Goal-First** — Define success before starting
2. **Hypothesis Plurality** — NEVER just one idea (minimum 3)
3. **Minimum Viable Experiments** — Smallest test that teaches
4. **Falsifiability** — Experiments must be able to fail
5. **Measure What Matters** — Only goal-relevant data
6. **Honest Analysis** — Compare to goal, not expectations
7. **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

1. **Goal** — What does success look like?
2. **Observe** — What do we know?
3. **Hypothesize** — At least 3 ideas
4. **Experiment** — Minimum viable tests
5. **Measure** — Collect goal-relevant data
6. **Analyze** — Compare to success criteria
7. **Iterate** — Adjust and repeat

**The answer emerges from the cycle, not from guessing.**
Files in this package (14)
  • Examples.md 4 KB
  • METHODOLOGY.md 16 KB
  • Protocol.md 11 KB
  • SKILL.md 4 KB
  • Templates.md 3 KB
  • workflows/AnalyzeResults.md 6 KB
  • workflows/DefineGoal.md 5 KB
  • workflows/DesignExperiment.md 8 KB
  • workflows/FullCycle.md 10 KB
  • workflows/GenerateHypotheses.md 6 KB
  • workflows/Iterate.md 8 KB
  • workflows/MeasureResults.md 6 KB
  • workflows/QuickDiagnosis.md 4 KB
  • workflows/StructuredInvestigation.md 6 KB

Versions

RepositoryScoreLicence
This page · ajbmachon/ajbm-skills100MIT
r3dlex/oh-my-auggie100Apache-2.0
researai/deepscientist100Apache-2.0
danielmiessler/personal_ai_infrastructure95MIT
danielmiessler/LifeOS95MIT
virtualian/pai95MIT
virtualian/pai95MIT
virtualian/pai95MIT

Database snapshot: 13.11.2026 · package version 763e0564159d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100thinking-science
    Hypothesis-driven experimentation loop. Formulates testable hypotheses, designs experiments, measures results, and iterates. [WHAT] Scientific method applied to any kind of question: formulate hypotheses, identify what would falsify them, design tests, analyse results, update…
  • 100hypothesis-tester
    Structured hypothesis formulation, experiment design, and results interpretation for Product Managers. Use when the user needs to validate an assumption, design an A/B test, or evaluate results. Trigger with "hypothesis", "A/B test", "experiment", "validate assumption", "test…
  • 100experiment-craft
    Use this skill when the user wants to debug, diagnose, or systematically iterate on an experiment that already exists, or when they need a structured experiment log for tracking runs, hypotheses, failures, results, and next steps during active research. Apply it to…
  • 100research-hypothesis
    Create, update, and manage hypothesis cards within an research project. Maintains the hypothesis graph (Mermaid diagram) and the catalog table. Handles parent-child relationships, status transitions, and result recording. Use when formulating a new hypothesis, recording…
  • 90research-experiment
    Guide experiment design, execution tracking, and result recording for an research hypothesis. Helps set up reproducible environments, plan minimal experiments, track progress against the timebox, and formally record outcomes. Use when starting an experiment for a hypothesis,…
  • 100beta-test-cycles
    This skill should be used when the user asks to "run beta test cycle", "run next cycle", "test static patterns", "analyze test failures", "improve pass rate", or wants to systematically improve command generation quality through iterative testing and pattern refinement. Provides…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.