DEV Community

Cover image for Day 15 of 60: I Built a Multi-Agent Research System That Researches, Writes and Reviews Reports in Under 60 Seconds
Cess Mbugua
Cess Mbugua

Posted on

Day 15 of 60: I Built a Multi-Agent Research System That Researches, Writes and Reviews Reports in Under 60 Seconds

Today's build is the most sophisticated thing I've shipped so far.

A single AI call handles one task well. But complex research requires four fundamentally different cognitive tasks; finding information, synthesising it, writing a structured report, and reviewing its quality. Each needs different instructions. Different tools. Different evaluation criteria.

So I stopped using one agent and built three.


## The Real World Problem

When you send a complex research question to a single Claude prompt you get a single pass. The response might be well-written but poorly researched. Or well-researched but poorly structured. Or both good but containing errors nobody checked.

In the real world every high-quality deliverable goes through multiple specialist hands. Research agencies, law firms, consulting firms, and newsrooms all use teams, not because one person cannot do the work, but because specialisation and review produce dramatically better results.


## The Analogy That Made It Click

Think of a newspaper editorial team. When a breaking story comes in three people handle it:

The journalist: gathers facts, interviews sources, finds the data. Does not write the final article.
The writer: takes the journalist's notes and turns them into a polished, structured article. Was not at the scene.
The editor: reads the finished article before it publishes. Checks facts, identifies gaps, suggests improvements. Did not gather or write anything.

Three specialists. Three distinct roles. One final product better than any one of them could produce alone.


## How the System Works

Topic comes in
↓
Researcher Agent: searches the web via Tavily
                   summarises findings
↓
Writer Agent: takes research output
               produces structured written report
↓
Reviewer Agent: reads the report
                 returns quality score + specific improvements
↓
Final reviewed report delivered in under 60 seconds
Enter fullscreen mode Exit fullscreen mode

The cast:

  • Researcher = The journalist: finds information via Tavily web search
  • Writer = The writer: turns research into a structured report
  • Reviewer = The editor: checks quality and flags improvements
  • Orchestrator = The news desk: coordinates handoffs between agents
  • Claude = The intelligence powering all three with different instructions
  • Tavily = The press pass: gives the Researcher access to live web search

## What I Learned

The biggest shift today was thinking in roles not prompts. Every agent has its own identity, its own instructions, and its own output format. The output of each becomes the input of the next.

This is the architecture behind every serious AI product being built in 2026. Content agencies, research firms, legal teams, and marketing departments all need research-to-report pipelines that don't require a human at every step.


**🔗 Full project on GitHub → https://github.com/mbuguacessy-glitch

45 more to go.**

ai #multiagent #claudeapi #python #automation #learninpublic #buildinpublic #100DaysOfCode

Top comments (0)