experiment-plan

Plan screening and confirmation training experiments with precommitted metrics, budgets, and decision rules.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill experiment-plan-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment-plan
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/skills/experiment-plan
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill experiment-plan-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research experiments often suffer from moving goalposts, cherry-picked metrics, and uncontrolled comparisons that invalidate results. This Skill enforces a disciplined experiment planning process that fixes the metric, controls, budget, and decision rule before any training run launches. ## Core Features & Use Cases - Screening Run Planning: Design cheap small-scale training screens that compare the active candidate against a frozen baseline while changing only the mapped adaptation, with precommitted pass thresholds and valid-failure routes. - Confirmation Run Planning: Define full-budget confirmation runs with frozen code and hyperparameters, predetermined seeds, strong comparators, and precommitted aggregation and promotion thresholds. - Validity Protection: Keep held-out labels out of candidate selection, forbid protocol changes after results, and record backend, runtime, launch command, and run id bookkeeping in research/EXPERIMENT_PLAN.md. - Use Case: Before launching a training run to test a new adaptation hypothesis, use this Skill to write a plan that states which claim the run tests, what success means, and what a valid failure looks like, so the result can support or reject the hypothesis without ambiguity. ## Quick Start Ask the agent to plan a screening experiment for the active candidate and write the plan to research/EXPERIMENT_PLAN.md before launching training.

Frequently Asked Questions about experiment-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a machine learning screening experiment?▼

Use the smallest training setup that preserves the mechanism under test: compare the candidate against a frozen baseline, change only the mapped adaptation, use a representative subset with predetermined seeds, and precommit the pass threshold and invalid-run conditions before launch.

What is the difference between a screening run and a confirmation run?▼

A screening run uses a cheap small-scale setup to select candidates and cannot support a final performance claim. A confirmation run uses the full training schedule, frozen code and hyperparameters, at least three predetermined seeds, and all required strong comparators to support promotion decisions.

How many seeds should a confirmation experiment use?▼

Use the project-prescribed seeds when a seed rule exists. When the project has no seed rule, use at least three predetermined seeds, and precommit the aggregation, uncertainty handling, and statistical test before observing results.

Can I change the candidate after seeing confirmation results?▼

No. Candidate changes after observing confirmation results are forbidden; a changed candidate must go through screening again. Follow-up comparisons also cannot become promotion prerequisites after results are seen.

When should the askgpt-governor oracle be consulted during experiment planning?▼

Consult it only when an unresolved choice materially changes evaluation obligations or compute commitment and cannot be settled from the research contract, literature, screening evidence, or project rules. Do not escalate ordinary seed counts, runtime estimates, or thresholds already fixed by the protocol.