# Engineering Review Implementation-ready before it reaches engineering ## How it works 1. ### Share the prototype Point the agent at a prototype along with your codebase context. It understands your existing architecture and tech stack. 2. ### Evaluate feasibility The agent assesses implementation complexity, identifies reusable components, flags state management challenges, and estimates engineering effort. 3. ### Get an implementation brief Receive a structured review covering architecture recommendations, component mapping, risk areas, and a suggested implementation approach. ## Why use Engineering Review ### No feasibility surprises Catch "this would take 3 months, not 3 days" issues before they derail the project. ### Component reuse Identifies existing components and patterns in your codebase that can be reused, reducing implementation effort. ### Better handoff conversations Engineering reviews surface the right questions early, making design-engineering handoff conversations productive. ### Architecture alignment Ensures the proposed design works within your existing architecture rather than requiring unexpected refactors. ## When to use Engineering Review ### Pre-handoff feasibility check You want to validate that a design is buildable before presenting it as the approved direction. Review this dashboard prototype against our React codebase. What can reuse existing components and what needs to be built from scratch? ### Complexity estimation You need to understand the engineering effort before committing to a design direction. Evaluate the implementation complexity of these two design options and tell me which one is significantly cheaper to build. ### State management review The design involves complex interactions and you want to ensure the state management is well thought through. Review the state management implications of this multi-step wizard prototype. Where are the tricky parts? ## More from your Engineering Partner ### Implementation Handoff View skill.