ablation-planner

# Ablation Planner Systematically design ablation studies that answer the questions reviewers will ask. The reviewer agent leads the design; the local executor reviews feasibility and implements. ## Context: $ARGUMENTS ## Constants - **REVIEWER_MODEL = `gpt-5.4`** - Used via a secondary Codex agent for reviewer-style ablation design. ## When to Use - Main results pass `/result-to-claim` with `claim_supported = yes` or `partial` - The user explicitly requests ablation planning - `/auto-review-loop` identifies missing ablations ## Workflow ### Step 1: Prepare Context Read available project files to build the full picture: - Method description and components (from `docs/research_contract.md`, project notes, or method docs) - Current experiment results (from `EXPERIMENT_LOG.md`, `EXPERIMENT_TRACKER.md`, or W&B) - Confirmed and intended claims (from `/result-to-claim` output or project notes) - Available compute resources (from server notes, run configs, or user-provided budget) ### Step 2: Secondary Codex Designs Ablations ```text spawn_agent: model: REVIEWER_MODEL reasoning_effort: xhigh message: | You are a rigorous ML reviewer planning ablation studies. Given this method and results, design ablations that: 1. Isolate the contribution of each novel component 2. Answer questions reviewers will definitely ask 3. Test sensitivity to key hyperparameters 4. Compare against natural alternative design choices Method: [description from pr...