What problem does it solve?
It prevents costly implementation mistakes by forcing early, critical review of technical pipeline designs for architectural correctness, performance risks, integration gaps, and missing requirements.
Core Features & Use Cases
- Hexagonal architecture compliance checks: aggressively flags dependency-direction violations and leaky layering as CRITICAL.
- Efficiency & scalability scrutiny: challenges over-engineering, redundant calls, and likely bottlenecks in the proposed flow.
- Risk and impact assessment: identifies breaking-change hazards, side effects, and what regression testing will be needed.
- Mandatory layer completeness verification: ensures the design covers UI, inbound adapters, and any data/seed components when applicable, marking gaps as CRITICAL — INCOMPLETE DESIGN.
- Auth and external protocol realism: verifies OAuth/MCP discovery, issuer alignment, and credential storage paths; otherwise marks as UNVERIFIED.
- External dependency failure modes: requires explicit handling for 401/503/timeouts plus clear degradation vs error behavior, marking omissions as CRITICAL.
- Local dev and partial-access deployment strategy: requires mocks/fakes and fallback wiring so the system still starts when a dependency is missing; omissions are CRITICAL.
Quick Start
Ask the pipeline designer to provide the proposed design document, then run pipeline-design-reviewer to produce a critical, actionable set of fixes before implementation begins.
