executing-plans-review

To detect design drift during task execution, run a verification hook after each task completes to compare implementation outputs against design specifications and report discrepancies. This validates alignment and updates session state.

Plan drift detection is the process of comparing completed task outputs against the original design document to identify discrepancies. It ensures implementation remains compliant with design specifications throughout the execution lifecycle.

You verify task output against a design document by triggering a post-task verification hook. This mechanism reads the design doc and task outputs, performs compliance checks, and generates a drift report to guide handoffs.

State synchronization during per-task execution works by reading and updating session state after task verification. It applies drift analysis results to update visual progress and guide the decision for the next task handoff.

You need to run verification checks after each task completes during a collab session. This per-task execution timing enables immediate drift analysis and design compliance checks before proceeding to the next handoff.

Yes, plan verification operates without external dependencies. It functions by reading the design document and task outputs directly within the Mermaid Collab workflow to execute drift analysis and compliance checks.