| name | eda-hypothesis-experiment-designer |
| description | Convert research ideas into falsifiable hypotheses and experiment plans with metrics, controls, pass/fail criteria, and confounder mitigation. |
EDA Hypothesis Experiment Designer
When to use
Use this skill after idea selection and before method implementation or expensive experiment submission.
Knowledge And Tool Interaction
- If the task needs shared KB or tool lookup before formalizing hypotheses, delegate that step to
eda-context-accessor.
- Use idea memos, KB context, and prior evidence artifacts as the basis for falsifiable hypothesis design instead of inventing hypotheses from scratch.
- When related local experiments already exist, use
eda-experiment-phenomenology-analyst artifacts so hypothesis design reflects repeated practical evidence rather than only theoretical intuition.
- Write experiment-design outputs so downstream implementation and validation skills can consume them directly.
Outputs
hypothesis_experiment_matrix.tsv
experiment_design_note.md
promotion_gate.md
Hard rules
- Each hypothesis must have explicit disproof condition.
- Metrics must match decision question (not just easy-to-collect metrics).
- Include at least one negative-control or ablation check when feasible.
Operational References
- Load
references/assumption-to-hypothesis.md when extracting assumptions from an idea memo and turning them into falsifiable statements.
- Load
references/matrix-rules.md when filling the experiment matrix columns, metrics, confounders, and pass/fail rules.
- Load
references/promotion-gate-design.md when defining the evidence needed to move from hypothesis to implementation.