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?
- Get interviewedLet a planning chat ask what the problem is, who uses it and what each stage hands to the next.
- Write the contractTurn answers into a spec listing each agent's job, inputs, outputs and tests.
- Hand over the specAsk the coding agent to build from it and approve permissions as it works.
- Run on real dataFeed a messy file through the full pipeline and read every output.
- 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.
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?
Why so many tests?
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.