ablation-planner

Designing ablations from a reviewer perspective involves coordinating a secondary Codex reviewer agent with a local executor to assess feasibility and implement changes. It produces a structured Ablation Plan with component modifications, hyperparameter explorations, and estimated compute for manuscript submission.

The best way to plan experimental ablations is applying this skill when main results pass claim-supported criteria. It guides reviewer-focused designs and feasibility checks between a reviewer agent and local executor, outputting an Ablation Plan suitable for recording in EXPERIMENT_LOG.md.

Yes, you need main results to pass claim-supported criteria before planning ablations. The skill applies specifically when this status is met, guiding reviewer-focused experimental designs and feasibility checks to validate the claims your manuscript makes.

Yes, delegating ablation design to a secondary Codex reviewer agent while the local executor assesses feasibility and implements changes is supported. This coordination produces a structured Ablation Plan with component-level changes, hyperparameter explorations, and estimated compute.

An ablation plan should include component-level changes like removals or replacements, hyperparameter explorations, and estimated compute. It generates a structured record suitable for EXPERIMENT_LOG.md to validate claims and strengthen your manuscript submission against reviewer questions.