experiment-plan

Convert research proposals into claim-to-evidence experiment roadmaps with run order and budget.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lightrain-a/medtrace-aris --skill experiment-plan-lightrain-a
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-plan
Source: https://github.com/lightrain-a/medtrace-aris/tree/main/.vendor/aris/skills/experiment-plan
Command: npx skills add https://github.com/lightrain-a/medtrace-aris --skill experiment-plan-lightrain-a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps transform a research idea into a structured, claim-driven set of experiments that can credibly defend what the paper claims—without bloating into an unfocused benchmark list.

Core Features & Use Cases

  • Claim map to evidence targets: freezes primary/supporting claims and defines what minimum evidence would make a reviewer believe them.
  • Compact experimental storyline: selects and prioritizes core experiment blocks (anchor result, novelty isolation, simplicity, frontier necessity, and diagnostics) for main paper, appendix, or cut.
  • Run order and budget planning: produces a practical milestone-based execution order with compute/risk considerations and creates an experiment tracker for execution.

Quick Start

Run experiment-plan to generate refine-logs/EXPERIMENT_PLAN.md and refine-logs/EXPERIMENT_TRACKER.md from your refined proposal context in the project workspace.

Frequently Asked Questions about experiment-plan

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

FAQPage Schema
How do I design an ablation matrix and evaluation protocol for a research proposal?

Designing an ablation matrix and evaluation protocol starts by freezing primary claims and mapping them to minimum evidence targets. You then structure core experiment blocks for novelty isolation and diagnostics, prioritizing must-run versus nice-to-have milestones for paper-ready validation.

What is the best way to plan compute budgeting for LLM or diffusion model experiments?

Planning compute budgeting for LLM or diffusion experiments involves creating a practical milestone-based execution order. You map run order and risk considerations against available compute resources to ensure efficient validation without bloating into an unfocused benchmark list.

How do I map paper claims to experimental evidence targets for reviewer validation?

Mapping paper claims to evidence targets requires freezing your primary and supporting claims first, then defining exactly what minimum evidence would convince a reviewer. This produces a paper-ready claim map separating core blocks from appendix-only diagnostics.

Can I use this experiment planning approach for both RL and VLM research contributions?

Yes, experiment planning applies directly to RL, VLM, LLM, and Diffusion contributions. It converts refined method ideas into a structured, claim-driven experiment roadmap with run order, compute considerations, and an execution tracker written to refine-logs.

How to prioritize must-run versus nice-to-have experiments for a paper submission?

Prioritizing must-run versus nice-to-have experiments involves categorizing core blocks into anchor results, novelty isolation, and frontier necessity. You select which blocks belong in the main paper, appendix, or should be cut based on milestone risk and compute constraints.

Why does my experiment plan result in an unfocused benchmark list instead of defendable claims?

An unfocused benchmark list happens when experiments lack claim-driven structure. To build defendable experiments, you must freeze primary claims early, map them to specific evidence targets, and organize runs into a compact experimental storyline with clear must-run milestones.