# AI Agent Orchestration for Coding Workflows

> fabriqa.ai coordinates AI coding agents across native specs, implementation tasks, reviews, handoffs, and provider context.

fabriqa.ai orchestrates agent work across planning, coding, testing, and review. The goal is not to replace Claude Code, Codex, GitHub Copilot, Cursor, Kiro, or OpenCode. The goal is to give teams one spec-native environment for using them together.

## What Orchestration Looks Like

### Shared intent

Every agent starts from the same spec. Goal, constraints, and acceptance criteria are explicit, so no agent has to infer the real intent from a chat history another agent cannot see.

### Visible handoffs

Every handoff is on one timeline. Teams can track what each agent is doing, where work moved next, and what still needs human review without copy-pasting between terminals or losing provider context.

### Free provider choice

Teams can use ACP providers, BYOK keys, subscriptions, direct API models, Ollama, OpenRouter, and local models in one workflow. The shared delivery context, cost visibility, and permissions stay coherent.

## Why Coordination Matters

Running several agents at once is only useful if they are working toward the same goal. fabriqa.ai makes the spec the coordination surface: tasks come from it, reviews refer back to it, and handoffs keep the original product intent intact.

## Related Pages

- [Multi-agent coding workflows](https://fabriqa.ai/multi-agent-coding-workflows.md)
- [Spec-driven development](https://fabriqa.ai/spec-driven-development.md)
- [Unified AI coding tools](https://fabriqa.ai/unified-ai-coding-tools.md)