pipeline-coder

To implement production code from an approved design, map affected components into a hexagonal architecture structure spanning Adapters, Application, and Domain layers, enforcing repository conventions for naming, exceptions, and dependency injection.

Multi-agent identity handling requires using the Identity object within multi-agent modules while strictly preventing user_id from leaking beyond adapter boundaries to maintain correct multi-agent identity isolation.

Start coding a Phase 3 implementation task by providing the approved Phase 2 design and any Code Reviewer or QA feedback to the AI, which performs a pre-implementation audit and reuses existing code before writing production-ready implementation.

Quality gates enforced during production code generation include verified port and interface alignment, strict code reuse checks, correct Identity usage, mandatory type hints, and docstrings applied throughout the hexagonal architecture structure.

Yes, a strict pre-implementation audit is required before converting a design into production code to verify port and interface alignment, assess existing code reuse opportunities, and ensure compliance with hexagonal architecture conventions.

Pipeline implementation breaks because multi-agent identity rules require user_id to remain strictly within adapter boundaries, and leaking it beyond adapters violates the hexagonal architecture isolation enforced during the pre-implementation audit.