review-plan

To review an implementation plan, extract the tech stack and project structure from the repository, then launch parallel assessments across six dimensions: feasibility, security, performance, maintainability, test coverage, and design-pattern consistency.

Assessing technical feasibility and maintainability involves evaluating the implementation plan against existing project patterns and architecture, identifying potential risks early to reduce rework and ensure long-term code maintainability.

Generate an updated project plan by synthesizing review findings with severity labels into actionable recommendations, then output a revised plan and a detailed changelog aligned to existing project structure and conventions.

Yes, evaluating test coverage and performance scalability from a project plan is possible by analyzing the proposed implementation steps and tech stack context to identify gaps and propose concrete updates before development begins.

No specific dependencies or components are required to review implementation plans, as the process gathers necessary context directly from the repository, including the base branch, tech stack, and project structure.

Automated plan reviews may not be suitable when the repository lacks a structured implementation plan, tech stack documentation, or clear project structure, as the assessment relies on extracting this context to evaluate feasibility and design consistency.