cto-plan-reviewer

To review architecture decisions in plan.md, you need a CTO-grade evaluation that applies ADR-inspired guidance to verify system design choices and alignment with team patterns. This process identifies architectural risks and suboptimal technology choices before execution begins.

Tech debt assessment is the detection and mitigation planning of long-term maintenance risks within your execution plan. You need it during tracks involving architecture decisions, technology choices, integrations, or infrastructure changes to catch suboptimal patterns early.

Evaluating integration readiness requires anticipating complexity, vendor impact, and costs for planned technology choices. An architecture review assesses observability considerations by ensuring monitoring, logging, and testing are planned from the outset within your spec.md.

Yes, applying ADR-inspired guidance to your plan.md verifies system design decisions and alignment with team patterns. This architecture assessment catches architectural risks, tech debt, and suboptimal technology choices before code is written.

Plan evaluation limitations include its reliance on the completeness of plan.md and spec.md context. It specifically targets tracks involving architecture decisions and infrastructure changes, meaning it may not catch runtime tech debt or implementation-level architectural risks emerging during coding.