mcpField
A
analysis-planning

analysis-planning

github.com/nimrodfisherData & databases504226 installsUpdated 5w ago
Repository

About analysis-planning

A planning skill for data analysts to turn analysis requirements into a sequenced, time-estimated plan. It identifies data dependencies, parallel steps, risks, and optional stakeholder kickoff needs before analysis begins.

Key features

  1. 01Breaks questions into answerable sub-questions
  2. 02Maps data needs and availability
  3. 03Sequences steps and identifies parallel work
  4. 04Estimates effort and records risks
  5. 05Creates analysis and kickoff plans

Use cases

  1. 01Planning multi-step analysis before accessing data
  2. 02Checking whether a project can meet its deadline
  3. 03Surfacing data gaps and dependencies early

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nimrodfisher/data-analytics-skills --skill analysis-planning

After installing, type/analysis-planningin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
analysis_plan_template.md
kickoff_doc_template.md
references/
effort_estimation.md
risks_dependencies.md
scoping_framework.md

Details

From the project README

When to use

After requirements are gathered and before any data is touched. Planning is especially important when the analysis involves multiple steps, uncertain data availability, or a tight deadline where sequencing matters. A 15-minute planning session prevents hours of wrong-direction work.

Process

  1. Decompose the question — break the business question into sub-questions using references/scoping_framework.md; each sub-question should be answerable with a single data pull or calculation.
  2. Identify data dependencies — for each sub-question, list the required tables/datasets and assess availability (confirmed / likely / unknown); flag blockers early.
  3. Sequence the work — order sub-questions so that each output feeds the next; identify which steps can run in parallel.
  4. Estimate effort — use references/effort_estimation.md to assign time estimates per step; sum to a total and compare against the deadline.
  5. Log risks and dependencies — use references/risks_dependencies.md to document anything that could delay or invalidate the plan (data gaps, external approvals, methodology uncertainty).
  6. Produce the plan — fill in assets/analysis_plan_template.md; for projects with stakeholder kickoffs use assets/kickoff_doc_template.md.

Inputs the skill needs

  • Analysis brief or requirements doc (from stakeholder-requirements-gathering skill)
  • Available data sources
  • Deadline and resource constraints

Output

  • Completed analysis plan with sequenced steps and time estimates (analysis_plan_template.md)
  • Kickoff doc for stakeholder alignment (optional, kickoff_doc_template.md)
  • Risk / dependency log

Comments

Markdown supported