experiment-plan

Create claim-driven experiment roadmaps with evaluation blocks, metrics, and run orders.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill experiment-plan-hve4638
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: experiment-plan
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/aris/skills/experiment-plan
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill experiment-plan-hve4638

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Experiment Plan skill turns a refined research proposal or method idea into a concrete, claim-driven roadmap of experiments, enabling systematic validation for publication or product-direction decisions.

Core Features & Use Cases

  • Convert a stable proposal into a structured plan that links primary and secondary claims to concrete experiments.
  • Define run orders, data requirements, evaluation metrics, baselines, and risks in a compact, reusable format.
  • Produce artifacts like refine-logs/EXPERIMENT_PLAN.md and refine-logs/EXPERIMENT_TRACKER.md to guide execution and tracking.

Quick Start

Provide your refined proposal and I will generate a detailed experiment plan and tracker.

Frequently Asked Questions about experiment-plan

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

FAQPage Schema
How do I create an experiment plan to validate research claims?

To create an experiment plan, define primary and secondary claims, then map them to concrete evaluation blocks, datasets, metrics, and run orders. This generates a structured roadmap with must-run blocks, success criteria, and reproducible budgets to validate your research proposal.

What is a claim-driven experiment roadmap and when do I need one?

A claim-driven experiment roadmap systematically connects your research contributions to specific experiments, datasets, and metrics. You need one when converting a refined research proposal or method idea into a structured validation plan for publication or product-direction decisions.

How do I structure run orders and evaluation blocks for research experiments?

Structure run orders and evaluation blocks by defining primary and secondary claims, then mapping them to a minimal set of must-run blocks with clear success criteria. Include baselines, data requirements, evaluation metrics, and risk mitigations in a compact, reusable format.

Can I use this methodology to plan experiments for product direction decisions?

Yes, this methodology applies to product direction decisions by turning a refined method idea into a concrete, claim-driven roadmap of experiments. It enables systematic validation through structured plans with milestones, reproducible budgets, and clear success criteria.

What artifacts are produced when planning rigorous experiments?

Planning rigorous experiments produces two main artifacts: an Experiment Plan and an Experiment Tracker. These artifacts guide execution and tracking by documenting run orders, reproducible budgets, milestones, and risk mitigations for systematic validation.

Do I need a refined research proposal before generating an experiment plan?

Yes, a refined research proposal or stable method idea is required before generating an experiment plan. The Skill converts your refined proposal into a structured plan linking primary and secondary claims to concrete experiments with defined metrics and baselines.