replan

To update an approved project plan when assumptions break, you record the validated divergence evidence in a replan log. This process captures what went wrong and drafts a revised approach without immediately jumping into implementation.

Amending an approved proposal before execution requires a pre-work amendment that updates the original plan while preserving accountability. You brainstorm a revised plan triple, stress-test it, and log the changes after user approval.

To safely revise a work unit plan midstream without losing auditability, you draft a replan entry capturing the Original plan, What changed, and the New plan. This entry is stress-tested and hard-gated before being written to the replan log.

Yes, updating project scope mid-work requires hard-gating before writing the replan log. The system stress-tests the revised plan triple and only commits the changes to the replan.md file after explicit user approval is granted.

You should avoid using a formal replan workflow for scope changes when you cannot resolve the target work unit or read the necessary proposal and scratchpad context. Without this baseline data, stress-testing revised plans is not possible.

Yes, you can update proposal success criteria during the replan process. After drafting and stress-testing the revised plan triple, the workflow optionally updates the proposal success criteria before finalizing the replan log entry.