Executing Analysis

Executing the Analysis

Overview

Load the pre-registered plan, review it critically, execute all steps exactly as registered, report when complete.

Announce at start: "I'm using the executing-analysis skill to run this analysis."

Note: Tell your human partner that Science Superpowers works much better with access to subagents — the protocol-compliance and rigor reviews catch more when run by fresh agents. If subagents are available, use science-superpowers:subagent-driven-analysis instead.

Prerequisite

The plan MUST be pre-registered and frozen (science-superpowers:preregistering-analysis) and the workspace set up (science-superpowers:setting-up-reproducible-analysis). If either is missing, stop and do it first. Executing before freezing turns the analysis exploratory.

The Process

Step 1: Load and Review

• Read the analysis plan and the frozen pre-registration.
• Review critically — any concern about the design, the decision rule, or feasibility?
• If concerns: raise them with your human partner before starting. A change to the registered analysis is a documented deviation and renders that part exploratory.
• If no concerns: create a TodoWrite with all steps and proceed.

Step 2: Execute Steps

For each step:

• Mark in_progress.
• For nontrivial estimators: validate the pipeline on known/simulated data first.
• Run the step exactly as registered. Keep the seed. Read immutable raw / named derived; write a new artifact.
• Validate the output (shape, ranges, counts) — nothing changes silently.
• Apply the registered decision rule as written; do not re-decide it after seeing the number.
• Use science-superpowers:verifying-results-before-claiming before marking done.
• Commit. Mark completed.

Checkpoints

After each natural group of steps (e.g., data prep, then primary model), pause and report results to your human partner before continuing. Keep confirmatory and exploratory results clearly separated in every report.

Step 3: Complete

After all steps complete and verified:

• Use science-superpowers:requesting-red-team-review on the whole result.
• Then science-superpowers:reporting-and-archiving-findings.

When to Stop and Ask

STOP immediately when:

• A result is surprising, impossible, or contradicts a sanity check → use science-superpowers:investigating-anomalous-results (do NOT quietly drop data or tweak parameters)
• The plan requires deviating from the pre-registration to proceed
• A validation fails repeatedly
• An instruction is unclear

Ask rather than guess. A guess that changes the analysis silently destroys the result's credibility.

Remember

• Pre-registration frozen before execution
• Validate pipelines on known data
• Run steps exactly as registered; never silently deviate
• Label anything unregistered as exploratory
• Don't skip validation or verification
• Stop on anomalies; investigate by root cause

Integration

Required workflow skills:

• science-superpowers:setting-up-reproducible-analysis — run first
• science-superpowers:preregistering-analysis — frozen before execution
• science-superpowers:investigating-anomalous-results — on surprising results
• science-superpowers:verifying-results-before-claiming — before any completion claim
• science-superpowers:reporting-and-archiving-findings — after all steps complete