design-review-validation

You can validate implementation against detailed design by running a structured quality gate workflow spanning COMPARE, VERIFY, L4_ALIGN, and APPROVE phases to detect deviations and maintain traceability during the DO cycle.

Design-implementation deviations are misalignments between plan artifacts and implementation files. You track them by reading design documents and source code to surface gaps, then documenting decisions and optionally updating the plan when deviations are approved.

To check L4 requirements alignment during the DO phase, run the L4_ALIGN workflow to compare implemented software against L4 requirements, which prompts gap handling and enforces compliance through read and analysis operations.

Yes, you can update the project plan when intentional design deviations are approved. The validation workflow supports optional Edit operations to modify plan artifacts, keeping documentation synchronized with approved implementation decisions.

No, the design review validation workflow is technology-agnostic. It requires no external dependencies and uses standard read, grep, and edit operations to validate implementation files against design artifacts across any tech stack.

The best way to enforce a design compliance quality gate is applying a phase-driven validation process that compares implementation files against detailed design artifacts, detects deviations early, and maintains traceability through structured approval workflows.