gpd-revise-phase

To supersede a completed project phase, you initiate a controlled workflow that marks the old phase as superseded, documents learnings in SUPERSEDED.md, and creates a replacement phase inheriting valid context.

Handling dependency propagation when revising an earlier phase requires updating ROADMAP.md, STATE.md, and downstream phases to reflect the revision, ensuring state synchronization via the GPD CLI.

You need a phase supersession workflow in non-linear research when earlier results must be revisited and replaced, allowing you to address necessary changes while keeping original artifacts preserved for historical context.

Creating a replacement phase that inherits decisions involves initiating the revise-phase workflow with the target phase number and a reason, then planning the replacement phase to inherit valid decisions while addressing what needs change.

Yes, you need the GPD CLI to ensure phase supersession, dependency propagation, and state synchronization during the process, coordinating updates to downstream references and phase artifacts.