| name | code-data-analysis-scaffolds |
| description | Use when starting technical work requiring structured approach - writing tests before code (TDD), planning data exploration (EDA), designing statistical analysis, clarifying modeling objectives (causal vs predictive), or validating results. Invoke when user mentions "write tests for", "explore this dataset", "analyze", "model", "validate", or when technical work needs systematic scaffolding before execution. |
Code Data Analysis Scaffolds
Table of Contents
Purpose
This skill provides structured scaffolds (frameworks, checklists, templates) for technical work in software engineering and data science. It helps you approach complex tasks systematically by defining what to do, in what order, and what to validate before proceeding.
When to Use This Skill
Use this skill when you need to:
- Write tests systematically - TDD scaffolding, test suite design, test data generation
- Explore data rigorously - EDA plans, data quality checks, feature analysis strategies
- Design statistical analyses - A/B tests, causal inference, hypothesis testing frameworks
- Build predictive models - Model selection, validation strategy, evaluation metrics
- Refactor with confidence - Test coverage strategy, refactoring checklist, regression prevention
- Validate technical work - Data validation, model evaluation, code quality checks
- Clarify technical approach - Distinguish causal vs predictive goals, choose appropriate methods
Trigger phrases:
- "Write tests for [code/feature]"
- "Explore this dataset"
- "Analyze [data/problem]"
- "Build a model to predict..."
- "How should I validate..."
- "Design an A/B test for..."
- "What's the right approach to..."
When NOT to Use This Skill
Skip this skill when:
- Just execute, don't plan - User wants immediate code/analysis without scaffolding
- Scaffold already exists - User has clear plan and just needs execution help
- Non-technical tasks - Use appropriate skill for writing, planning, decision-making
- Simple one-liners - No scaffold needed for trivial tasks
- Exploratory conversation - User is brainstorming, not ready for structured approach yet
What Is It?
Code Data Analysis Scaffolds provides structured frameworks for common technical patterns:
- TDD Scaffold: Given requirements, generate test structure before implementing code
- EDA Scaffold: Given dataset, create systematic exploration plan
- Statistical Analysis Scaffold: Given question, design appropriate statistical test/model
- Validation Scaffold: Given code/model/data, create comprehensive validation checklist
Quick example:
Task: "Write authentication function"
TDD Scaffold:
def test_valid_credentials():
assert authenticate("user@example.com", "correct_pass") == True
def test_invalid_password():
assert authenticate("user@example.com", "wrong_pass") == False
def test_nonexistent_user():
assert authenticate("nobody@example.com", "any_pass") == False
def test_empty_credentials():
with pytest.raises(ValueError):
authenticate("", "")
Workflow
Copy this checklist and track your progress:
Code Data Analysis Scaffolds Progress:
- [ ] Step 1: Clarify task and objectives
- [ ] Step 2: Choose appropriate scaffold type
- [ ] Step 3: Generate scaffold structure
- [ ] Step 4: Validate scaffold completeness
- [ ] Step 5: Deliver scaffold and guide execution
Step 1: Clarify task and objectives
Ask user for the task, dataset/codebase context, constraints, and expected outcome. Determine if this is TDD (write tests first), EDA (explore data), statistical analysis (test hypothesis), or validation (check quality). See resources/template.md for context questions.
Step 2: Choose appropriate scaffold type
Based on task, select scaffold: TDD (testing code), EDA (exploring data), Statistical Analysis (hypothesis testing, A/B tests), Causal Inference (estimating treatment effects), Predictive Modeling (building ML models), or Validation (checking quality). See Scaffold Types for guidance on choosing.
Step 3: Generate scaffold structure
Create systematic framework with clear steps, validation checkpoints, and expected outputs at each stage. For standard cases use resources/template.md; for advanced techniques see resources/methodology.md.
Step 4: Validate scaffold completeness
Check scaffold covers all requirements, includes validation steps, makes assumptions explicit, and provides clear success criteria. Self-assess using resources/evaluators/rubric_code_data_analysis_scaffolds.json - minimum score ≥3.5.
Step 5: Deliver scaffold and guide execution
Present scaffold with clear next steps. If user wants execution help, follow the scaffold systematically. If scaffold reveals gaps (missing data, unclear requirements), surface these before proceeding.
Scaffold Types
TDD (Test-Driven Development)
When: Writing new code, refactoring existing code, fixing bugs
Output: Test structure (test cases → implementation → refactor)
Key Elements: Test cases covering happy path, edge cases, error conditions, test data setup
EDA (Exploratory Data Analysis)
When: New dataset, data quality questions, feature engineering
Output: Exploration plan (data overview → quality checks → univariate → bivariate → insights)
Key Elements: Data shape/types, missing values, distributions, outliers, correlations
Statistical Analysis
When: Hypothesis testing, A/B testing, comparing groups
Output: Analysis design (question → hypothesis → test selection → assumptions → interpretation)
Key Elements: Null/alternative hypotheses, significance level, power analysis, assumption checks
Causal Inference
When: Estimating treatment effects, understanding causation not just correlation
Output: Causal design (DAG → identification strategy → estimation → sensitivity analysis)
Key Elements: Confounders, treatment/control groups, identification assumptions, effect estimation
Predictive Modeling
When: Building ML models, forecasting, classification/regression tasks
Output: Modeling pipeline (data prep → feature engineering → model selection → validation → evaluation)
Key Elements: Train/val/test split, baseline model, metrics selection, cross-validation, error analysis
Validation
When: Checking data quality, code quality, model quality before deployment
Output: Validation checklist (assertions → edge cases → integration tests → monitoring)
Key Elements: Acceptance criteria, test coverage, error handling, boundary conditions
Guardrails
- Clarify before scaffolding - Don't guess what user needs; ask clarifying questions first
- Distinguish causal vs predictive - Causal inference needs different methods than prediction (RCT/IV vs ML)
- Make assumptions explicit - Every scaffold has assumptions (data distribution, user behavior, system constraints)
- Include validation steps - Scaffold should include checkpoints to validate work at each stage
- Provide examples - Show what good looks like (sample test, sample EDA visualization, sample model evaluation)
- Surface gaps early - If scaffold reveals missing data/requirements, flag immediately
- Avoid premature optimization - Start with simple scaffold, add complexity only if needed
- Follow best practices - TDD: test first, EDA: start with data quality, Modeling: baseline before complex models
Quick Reference
