plan-reviewer

To review an implementation plan for architectural soundness, analyze its structure, scope, and verifiability to enforce concrete file-level targets, commands, and automated validation criteria.

The No Magic Rule in technical design requires explicit file paths and concrete changes rather than vague direction, ensuring implementation plans maintain actionable specificity and clear boundaries.

Identify circular dependencies and data-migration risks in a system blueprint by performing an architectural risk assessment that evaluates atomic phasing, pattern violations, and safe testable component boundaries.

Yes, you can generate automated and manual verification steps during a software design review by evaluating the plan's specificity to produce concrete criteria that validate architecture against requirements.

You need to break an implementation plan into atomic phases and milestones when ensuring safe, testable components with clear boundaries during pre-implementation design reviews and system blueprints.