meow:plan-eng-review

Plan an engineering review by validating architecture decisions, code quality, tests, and performance. Generate a structured plan file, ASCII diagrams, and a prioritized TODO list to ensure alignment and surface risks before implementation begins.

An engineering design review for a major refactor should cover architecture changes, code quality, test coverage, and performance. It produces a clear plan file with risk assessment and actionable TODOs to guide developers through the implementation.

Conduct a code review on a branch by analyzing architecture decisions, code quality, tests, and performance. The review process outputs ASCII diagrams, a plan file, and a prioritized TODO list to assess risks and verify the design before implementation.

Yes, use an engineering review to verify test coverage and code quality for new features. The review workflow evaluates architecture decisions and performance, producing a structured plan file with risk assessment and a prioritized TODO list for developers.

Document architecture decisions and risk assessment by running a structured engineering review. It generates a clear plan file containing risk evaluation, ASCII diagrams for architecture, and a prioritized TODO list to ensure actionable implementation steps.

Yes, an engineering design review works for cross-team architectural changes. It applies to branches and design docs, providing structured design critique, risk assessment, and a prioritized TODO list to align scope across teams before implementation.