What problem does it solve? Research teams accumulate experiment runs and datasets but lack a disciplined, reproducible way to analyze them. This Skill enforces a structured analysis workflow where every question becomes a committed, executed report with named sources and a stated verdict, eliminating ad-hoc analysis and numbers reconstructed from memory. ## Core Features & Use Cases - Run-bound analysis: Follows a run's pre-registered analysis plan from its *_plan.md file when invoked with a run number. - Interview-first planning: For open-ended questions, it derives an analysis plan through batched questions and requires explicit researcher confirmation before writing code. - Executed notebook reports: Produces committed Jupyter notebooks with outputs (sources, question, method, findings, verdict) so researchers read rendered results without running cells. - Use Case: After run 183 finishes an ablation, invoke "/analysis 183" to execute its pre-registered plan and receive a committed notebook report with the verdict stated first. ## Quick Start Ask the assistant to analyze run 183 or pose an analysis question about your experiment data and confirm the proposed analysis plan.