How I built production quality gates into a multi-agent Claude Code workflow

How I built production quality gates into a multi-agent Claude Code workflow Published to dev.to — cross-post from GitHub 1. The problem: agents that write code but never review it When I started using Claude Code's Agent tool to dispatch subagents, I noticed a pattern quickly: the agent would write code, declare success, and move on. There was no review step unless I explicitly asked for one in the prompt — and prompts are unreliable. If the model was running low on context or the task was complex, the review step would get dropped. The deeper issue is that multi-agent systems are composable but not automatically accountable. You can chain code-writer → commit → push in a plan, but nothing in the default setup prevents a buggy implementation from being committed and pushed before a human or reviewer has seen it. The agent doesn't know what it doesn't know. I wanted a framework where review wasn't optional — where it was structurally impossible to skip. 2. CAST's hook-driven commit gat