← Back to library

Write a spec first, then have agents build your analysis kit

Bronson Elliott, a data analyst for thirty years, spent one evening answering an idea-generator agent and left with a 713-line specification. Claude Code then built five CSV task agents plus an orchestrator from that written document in roughly five hours.

  • OutcomeGo from messy CSV to cleaned data, charts, report and executive summary with one command, built by a coding agent from a written spec.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditBronson Elliott
View original
Works with
Claude CodeClaude

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • You repeat the same analysis steps on every dataset
  • You can describe the process but not code it
  • Stakeholders only read a one-page summary

Not for: Regulated reporting without independent checks; One-off questions a spreadsheet answers faster

What do you need, and what do you get?

You need

  • A written spec: agents, inputs, outputs, tests
  • Sample messy CSVs

You get

  • Cleaning, analysis, chart, report and summary agents
  • One command that runs the whole chain

How does it work, step by step?

  1. Get interviewedLet a planning chat ask what the problem is, who uses it and what each stage hands to the next.
  2. Write the contractTurn answers into a spec listing each agent's job, inputs, outputs and tests.
  3. Hand over the specAsk the coding agent to build from it and approve permissions as it works.
  4. Run on real dataFeed a messy file through the full pipeline and read every output.
  5. Use parts aloneCall single agents, such as the cleaner, when you only need one stage.

The prompt

Our own prompt, inspired by Bronson Elliott and written to work in Claude Code and Claude. Values in lime are placeholders.

Prompt0 variables
Interview me to write a specification for a data analysis pipeline. Ask one question at a time about: the problem, who uses the output, each stage from cleaning to executive summary, what each stage receives and returns, and how we will test it. When we are done, produce a spec with one section per agent (purpose, inputs, outputs, edge cases, tests) and a section on the orchestrator that chains them.

Inspired by Bronson Elliott: I Built a Complete Data Analysis Agent Suite in One Evening (Without Writing Code). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Passing tests prove the code does what the spec says, not that the analysis is right; check findings.
  • A vague spec produces vague agents; the analyst credits the long document for the result.

Our take

The lesson is in specifying, not coding. Spending an evening being questioned until the process was concrete paid off more than jumping into prompts. Most people jump straight into prompting the coding agent; Bronson instead let a planning chat question him until each stage's job, inputs, outputs and tests were written down. The long spec then did the heavy lifting, and the build itself took hours rather than weeks. The trap is reading green tests as proof the analysis is right. Tests confirm the code matches the spec, not that the findings are sound, so run a real messy file through the chain and read every output, ideally against totals you already know. Being able to call one agent alone, such as the cleaner, is a nice side benefit. Keep the spec under version control and update it whenever the data changes shape. For regulated reporting, add an independent check before anyone relies on the numbers.

Where the time goes back: The repeat chores of every analysis run, from cleanup to the exec summary, collapse into one command.

FAQ

Did he write code?
No. He reports approving permissions around twenty times and never stepping in to debug.
Why so many tests?
The spec asked for tests per component, which let the agent catch and fix its own failures.

Source and credit

Inspired by Bronson Elliott. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I Built a Complete Data Analysis Agent Suite in One Evening (Without Writing Code)
Creator
Bronson Elliott
Published on
bronsonelliott.substack.com (Substack)
Original date
Jan 24, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Fill PDF forms from your own documents with an agent

Upload a fillable PDF and the documents that hold the answers; the agent stages a value for each field, shows you the pending edits and saves the filled form.

Credit: Jerry Liu (@jerryjliu0)

Under an hour
Operations & AdminPrompt✓ AI dry run

Give your agent a one-page map of where your work lives

In about ten minutes, have a desktop agent read only your folder and file names, interview you about what it cannot see, and write a one-page CLAUDE.md or AGENTS.md map it reads before every job.

Credit: u/jonathanmalkin on r/AI_Agents

Minutes
Operations & AdminWorkflow✓ AI dry run

Hand a coding agent a contracted web extraction job

Have a coding agent write and run a low-token script that extracts the fields your contract requires from allowed sites, then review the file before you submit.

Credit: u/ColdPlankton9273 on r/ClaudeAI

Under an hour
Operations & AdminWorkflow✓ AI dry run

Compress two years of curriculum into one

Give an AI the full curriculum for an accelerated class, have it remove overlap, schedule the year, and build tests, worksheets and optional practice games.

Credit: Jon Hegreness (@JonHegreness_AZ)

An afternoon+
Operations & AdminPrompt✓ AI dry run

Fill forms from a source packet, then proof every one

Given a packet of facts and many similar forms, have an assistant fill each form and produce a checklist so you proof every submission before it goes out.

Credit: u/Remote_Tangerine_718 on r/ClaudeAI

Under an hour