Engineering·Sep 28, 2025·9 min read

5 Common Agentic Design Patterns

From 'ReAct' to 'Map-Reduce', a catalogue of proven patterns for building reliable AI applications.

Engineering Team
Engineering team at Bothive. Building the future of AI agent orchestration.

5 Agentic Design Patterns

Just as software engineering has "Singleton" and "Factory", Agent Engineering has patterns.

1. The ReAct Pattern

Reason + Act. The agent thinks, decides on an action, executes it, and observes the result. This is the default loop for most agents.

2. The Map-Reduce Pattern

Great for analyzing large documents.

  • Map: 10 agents read 10 pages each and summarize.
  • Reduce: 1 agent reads the 10 summaries and writes a final report.

3. The Reflector Pattern

An agent generates a draft. A second agent (Reflector) critiques it. The first agent revises.

4. The Router Pattern

A lightweight classifier agent decides which expert tool to call. "Is this a math problem or a history question?"

5. The Dynamic Memory Pattern

The agent queries its long-term memory store before acting, updating its context window with relevant facts.

Master these, and you master agents.

How to apply this inside Bothive

The practical move is to turn the idea into an agent contract: what the agent can see, what it can do, where it should ask for approval, and how the team will inspect the result. A good Bothive workflow is not just a prompt. It has memory, tools, channels, traces, and a clear boundary between autonomous work and human judgment.

Define the boundary

For engineering work, decide which decisions the agent can make alone and which actions need a teammate in the loop.

Attach real context

Connect docs, customer data, repositories, tickets, calendars, or APIs so the agent works from grounded information.

Ship through a channel

Expose the agent through web chat, API, Slack, WhatsApp, schedules, or internal workflows depending on where the work starts.

Watch the run

Use traces, tool-call history, usage, and failure logs to improve the agent after it meets real users.

01

Build

Turn the idea into a readable agent contract, workflow, or builder graph.

02

Deploy

Run it through Bothive channels, schedules, integrations, and API calls.

03

Observe

Use traces, usage, memory, and tool logs to improve the system over time.

Subscribe to our newsletter

Get the latest updates on AI agent orchestration, product releases, and engineering insights delivered to your inbox.

5 Common Agentic Design Patterns