writing-analysis-plans

writing-analysis-plans is a skill for Claude Code from zpower426/datapowers. It costs 34 tokens per session (1,331 once invoked), scanned A, original, MIT.

A writing guide for turning an approved analytical design into a detailed work plan. It breaks data-science work, such as exploration, validation, modeling, and reporting, into small executable tasks.

In plain words
What is it for?
Use it after brainstorming and design approval to write a complete analysis plan with specific files, outputs, commands, and verification steps.
Why use it?
It removes ambiguity about what an analyst or coding agent must read, produce, and verify. This makes each task independently actionable and easier to review.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the datapowers plugin — 20 skills, 3 commands, 3 agents, 1 hook shipped together

Good fit Use it after brainstorming and design approval to write a complete analysis plan with specific files, outputs, commands, and verification steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zpower426/datapowers/writing-analysis-plans
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add zpower426/datapowers --skill writing-analysis-plans
Clone the repo
git clone --depth 1 https://github.com/zpower426/datapowers

Made for: Claude Code.

Or install datapowers, the plugin that ships this one along with the rest of its 20 skills, 3 commands, 3 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for writing-analysis-plans

README.md
[![agentmods](https://agentmods.dev/badge/skills/zpower426/datapowers/writing-analysis-plans/github.svg)](https://agentmods.dev/skills/zpower426/datapowers/writing-analysis-plans)
Your own site
<a href="https://agentmods.dev/skills/zpower426/datapowers/writing-analysis-plans"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/writing-analysis-plans/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for writing-analysis-plans

Your own site · 80×15
<a href="https://agentmods.dev/skills/zpower426/datapowers/writing-analysis-plans"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/writing-analysis-plans.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01331
Opus 5 $0.00017 $0.00665
Sonnet 5 $0.00007 $0.00266
Haiku 4.5 $0.00003 $0.00133

Measured 10d ago against content hash eb0768bf0309, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

writing-analysis-plans scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/writing-analysis-plans/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing Analysis Plans

Convert an approved analytical design into a detailed, executable plan with no placeholders, no ambiguity, and no implicit context.

Checklist

  1. Load the design doc — read the spec from docs/datapowers/specs/
  2. Identify all work streams — EDA, validation, feature engineering, modeling, evaluation, reporting
  3. Decompose into tasks — 15-30 minutes each, independently executable
  4. Write each task with full specificity — no placeholders, no "similar to above"
  5. Add verification step to every task — how to confirm completion
  6. Self-review the plan — check coverage, placeholder scan, task size
  7. Save plandocs/datapowers/plans/YYYY-MM-DD-<topic>-plan.md
  8. User reviews plan — confirm before execution begins

Task Decomposition Rules

Every task must specify:

  • Exact files or data to read
  • Exact outputs to produce (file names, variable names)
  • Exact code or commands (no "write code to do X")
  • Verification — what to run/check to confirm success

❌ Bad Task

Task 3: Feature engineering
- Create features for the churn dataset
- Handle missing values
- Encode categoricals

This is useless. An agent cannot execute this without guessing.

✅ Good Task

Task 3: Numeric feature preprocessing
Files: data/train.csv, data/test.csv

Steps:
1. Load X_train from data/train_features.csv (saved in Task 2)
2. For columns ['age', 'tenure_months', 'monthly_charges']:
   - Clip outliers at [Q1 - 3×IQR, Q3 + 3×IQR] using training set quantiles
   - Impute with median (fit on X_train, transform X_test)
   - Apply StandardScaler (fit on X_train, transform X_test)
3. Save fitted imputer to artifacts/imputer_numeric.pkl
4. Save fitted scaler to artifacts/scaler_numeric.pkl
5. Save transformed training features to data/X_train_numeric.csv
6. Save transformed test features to data/X_test_numeric.csv

Verification:
- Run: python -c "import pandas as pd; df=pd.read_csv('data/X_train_numeric.csv'); print(df.isnull().sum())"
- Expected: all zeros (no nulls after imputation)
- Run: python -c "import pandas as pd; df=pd.read_csv('data/X_train_numeric.csv'); print(df.describe())"
- Expected: means near 0, stds near 1 (after scaling)

Read the full file on GitHub · 159 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 159 lines · 34 tokens per session scan A eb0768bf0309

Subscribe to this mod's changes

writing-analysis-plans is a skill published in the GitHub repository zpower426/datapowers (1 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,331 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.