executing-analysis-plans

Executes approved empirical analysis plans with validated steps and parallel robustness checks.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/lancegui/causal-powers --skill executing-analysis-plans-lancegui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-analysis-plans
Source: https://github.com/lancegui/causal-powers/tree/main/evals/prompt-pilot-state-did/transcripts/current/stage1/instructions/skills/executing-analysis-plans
Command: npx skills add https://github.com/lancegui/causal-powers --skill executing-analysis-plans-lancegui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Once an analysis brief or pre-analysis plan is approved, actually carrying it out is where empirical work quietly goes wrong: steps run out of order, robustness suites balloon into unconvincing specification walls, and parallel subagents silently redesign the analysis. This Skill drives faithful execution of the approved plan so results are validated, reconciled, and decision points reach the user instead of being settled silently. ## Core Features & Use Cases - Sequential spine with parallel fan-out: Builds and validates the dataset, estimates the primary specification in order, then dispatches independent robustness specs, placebo tests, and alternative designs to parallel subagents. - Disciplined robustness selection: Proposes roughly three checks that target the main identification threat and requires user approval before running, rather than fanning out an exhaustive menu. - Constrained subagent dispatch: Hands each subagent the exact pre-specified task, the data contracts to assert, a structured result format, and a rule to stop and report on any design decision. - Use Case: After a difference-in-differences pre-analysis plan is approved, use this Skill to build the analysis dataset, estimate the primary specification, run the approved placebo and robustness checks via subagents, and assemble a reconciled results table. ## Quick Start Run the approved analysis plan end to end, validating each step and dispatching the robustness checks to parallel subagents.

Frequently Asked Questions about executing-analysis-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an approved pre-analysis plan step by step?▼

Start from the approved brief or PAP, build and validate the analysis dataset first, then estimate the primary specification before any robustness work. Validate each step against data contracts and stop at any decision that would change the design, sample, or estimand.

How many robustness checks should an econometric analysis include?▼

A robustness suite should target roughly three checks that probe the single most credible threat to identification, not an exhaustive menu of specifications. Each check should have a real chance of failing; cosmetic control additions prove nothing and read as weak identification.

When should robustness checks run in parallel subagents versus inline?▼

Parallel subagent dispatch suits genuinely independent specifications such as placebo tests, alternative designs, and subsample cuts, since it isolates each spec's context. Inline execution keeps every step observable, which suits small or delicate runs; the choice is presented to the user up front.

What should a robustness subagent do when it hits a design decision?▼

The subagent must stop and report back rather than resolving the decision itself. Any change to design, sample, specification, or estimand routes to the user through an analysis checkpoint, since an autonomous subagent deciding silently is a redesign happening behind the user's back.

Can I run this analysis workflow without an approved plan?▼

No. Execution requires an approved analysis brief or pre-analysis plan; without one, the correct move is to return to question framing and plan approval first. Running an unapproved plan produces unvalidated results with no committed design to check against.