experiment-plan

# Experiment Plan: Claim-Driven, Paper-Oriented Validation Refine and concretize: **$ARGUMENTS** ## Overview Use this skill after the method is stable enough that the next question becomes: **what exact experiments should we run, in what order, to defend the paper?** If the user wants the full chain in one request, prefer `/research-refine-pipeline`. The goal is not to generate a giant benchmark wishlist. The goal is to turn a proposal into a **claim -> evidence -> run order** roadmap that supports four things: 1. the method actually solves the anchored problem 2. the dominant contribution is real and focused 3. the method is elegant enough that extra complexity is unnecessary 4. any frontier-model-era component is genuinely useful, not decorative ## Constants - **OUTPUT_DIR = `refine-logs/`** — Default destination for experiment planning artifacts. - **MAX_PRIMARY_CLAIMS = 2** — Prefer one dominant claim plus one supporting claim. - **MAX_CORE_BLOCKS = 5** — Keep the must-run experimental story compact. - **MAX_BASELINE_FAMILIES = 3** — Prefer a few strong baselines over many weak ones. - **DEFAULT_SEEDS = 3** — Use 3 seeds when stochastic variance matters and budget allows. ## Workflow ### Phase 0: Load the Proposal Context Read the most relevant existing files first if they exist: - `refine-logs/FINAL_PROPOSAL.md` - `refine-logs/REVIEW_SUMMARY.md` - `refine-logs/REFINEMENT_REPORT.md` Extract: - **Problem Anchor** - **Dominant contribution** - **Optional suppor...