# Production Task Decomposition: Multi-Agent Software Pipelines

Category: Agent Orchestration
Stack: Claude Code, Planner/Builder/Critic, GitHub Actions

## Overview
Separating responsibilities across planner, builder, and critic agents to deliver multi-service web platforms without hallucinated specifications.

## The Problem
Single-agent pipelines attempt to design, code, and test simultaneously, resulting in incomplete implementations and neglected edge cases.

## Production Rule
Strictly separate Planner, Builder, and Critic agents. The Critic must have access to independent test suites and veto authority over deployments.

## Code / Specification
File: `agent_decomposition.md`

```systems architecture
Agent 1 (Planner): Generates task specification and API interface definitions.
Agent 2 (Builder): Implements code matching the specification.
Agent 3 (Critic): Executes linter, type-checker, and automated tests. Rejects PR on any failure.
```