plan-review-workflow

Separating planning from implementation for complex refactors requires a two-session workflow that drafts a plan first, then enforces staff-level review to validate scope, risks, and tradeoffs before execution begins.

Documenting tradeoffs for architecture decisions is best handled by a plan capture workflow that records decisions during planning, applies drift recovery prompts, and guides staff review to ensure traceability before implementation.

Handling plan drift during feature improvement implementation relies on drift recovery prompts that detect deviations from the original plan, ensuring execution remains aligned with documented decisions and staff-approved scope.

A two-session workflow for staff-level review is needed when applying to refactors, architecture decisions, and feature improvements that require documented tradeoffs and force a planning phase before implementation begins.

This workflow is not suited for small code changes; it applies to complex changes like refactors and architecture decisions that demand staff-level vetting, documented tradeoffs, and a forced planning phase before implementation.

Drift recovery in a plan review workflow works by applying prompts during implementation that track deviations from the original plan, keeping execution aligned with documented decisions and staff-approved scope.