four-agent-pipelinelisted

# Four-Agent Pipeline One idea, four agents, zero line-by-line human review. The human does exactly two things: write the requirement in a machine-verifiable form (via the Specifier), and trust a welded-shut set of automated quality gates. Everything in between is agents keeping each other honest. Core philosophy: **don't review the process — gate the outcome.** ## When to Use This Skill - Building a non-trivial feature where "vibe-coded" output is not acceptable - Setting up spec-driven development with Gherkin acceptance criteria - Running a multi-agent workflow (Claude Code subagents, CrewAI, or four separate sessions with the same model) with clear role separation - Replacing or augmenting human code review with measurable quality gates ## The Pipeline ``` vague requirement (natural language) | v [1] SPECIFIER compiles requirement -> Gherkin acceptance criteria + DoD | (the ONLY output a human reviews; spec is frozen after sign-off) v [2] CODER minimal implementation -> all acceptance + unit tests green | v [3] REFACTORER structure only, never behavior -> complexity/dup/mutation targets met | v [4] ARCHITECT veto power -> per-gate PASS/FAIL with measured values | v auto-merge — human reviews the acceptance-criteria diff, never the code diff ``` Failures never stall on a human. Every FAIL is routed back to the responsible upstream agent with the measured value vs. thre