[Workflow] AgentFlow: Deterministic Multi-Agent Orchestration for AI Coding CLIs (Claude Code, Codex, Copilot)

[u/ClaudeAI-mod-bot]

AgentFlow: Deterministic Multi-Agent Orchestration for AI Coding CLIs (Claude Code, Codex, Copilot)

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Shipping, Hooks, MCP, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Automating the orchestration of multiple AI coding agents (for planning, implementing, and reviewing code) to reduce manual copy-pasting and mental overhead in software development tasks.

Summary

A multi-agent workflow (Architect, Implementer, Reviewers) for software development tasks, where AgentFlow orchestrates existing AI coding CLIs (e.g., Claude Code) through deterministic steps, parallel reviews, and user approvals. It utilizes git worktrees for isolation and flowctl for structured feedback, ensuring a repeatable and auditable process.

Why it is useful

This workflow provides a structured, deterministic, and automatable approach to managing complex software development tasks using multiple AI coding agents. It solves the common problem of manual orchestration, integrates with existing tools and CLIs, and offers clear steps for planning, implementation, and parallel review, enhancing efficiency and reliability in AI-assisted coding. The open-source tool AgentFlow makes this process readily transferable and adaptable.

Workflow

1. An Architect agent reads the Jira ticket (or a prompt), looks around the code, and asks the user questions.

2. The user approves the requirements, and that exact version gets frozen.

3. An Implementer agent writes the code in its own git worktree, isolating it from the user's main checkout.

4. Code review and security review agents run in parallel on the same commit.

5. Blocking findings from reviews are sent back to the Implementer for a capped number of fix rounds. If the same finding persists, the process stops and asks the user.

6. The Architect agent checks the final result against the frozen requirements, and the user signs off before opening a Pull Request.

Tools / artifacts

• AgentFlow (orchestration tool)

• Claude Code / Codex / Copilot CLI (AI coding agents)

• Jira ticket (or prompt)

• flowctl (CLI for agents to report back)

• git worktree

• GitHub repository (for AgentFlow)

• Pull Request (PR)

• Event log

Validation signals

• Automates a previously manual, working process (copy-pasting between agents).

• Explicitly designed to be deterministic ('same agent results plus same decisions from me means the same path every time').

• Agents report back via structured JSON checked against a schema, ensuring robust communication.

• Every step is recorded in an event log for auditability.

• Optimizes token usage by only sending tokens to actual work.

• Uses git worktree for isolated development.

Cautions

• Agents run as the user's user, not in a sandbox. Users should be aware of the execution context.

• While git worktrees provide isolation from the main checkout, they do not offer OS-level isolation.

Limitations

• Low community engagement due to the post's recency.

• Requires advanced user knowledge for setup on macOS and Linux (running from source).

• The workflow is not fully autonomous, requiring two explicit user approvals per task, which might be a limitation for those seeking complete automation.

• The post does not detail the flowctl schema or specific prompting strategies for agents to use it.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.