cto-plan-reviewer

To review an execution plan for technical debt and architecture flaws, use a CTO-level framework to assess design patterns, technology choices, and engineering excellence against organizational standards, generating a detailed technical review report.

A technical architecture review evaluates system design, architecture patterns, and technology standards within a proposed execution plan. It identifies potential technical debt and assesses new technology choices for risk and cost before implementation begins.

To evaluate a technical execution plan, you need to provide context from plan.md, spec.md, tech-stack.md, and product.md. These documents supply the necessary product specifications and technology details to conduct a comprehensive architecture review.

You need a CTO-level technical plan evaluation before a new feature is coded. This ensures the chosen architecture is scalable and maintainable, catching poor technology choices and preventing costly rework during the implementation phase.

A technical plan review assesses new technology choices by evaluating their necessity, implementation risk, and cost within the proposed architecture. It checks these choices against best practices and organizational standards to ensure engineering excellence.

Yes, you can quantify technical debt implications before implementation by conducting a technical architecture review. The review identifies potential debt introduced by the execution plan and suggests mitigation strategies to maintain system quality.