gpd-merge-phases

Invoke the skill with the source phase first and target phase second, for example merging phase 5 into phase 4. The workflow validates both phases, presents a merge plan, and waits for your confirmation before copying artifacts and updating the roadmap.

Pass the --dry-run flag with the merge command. It shows which artifacts would move and which results would combine without executing any file copies, roadmap edits, or commits.

Source plans are appended to the target phase with renumbered filenames and updated depends_on references, never overwriting existing target plans. Verification files are copied with a merged-from-phase prefix to preserve provenance.

The workflow includes idempotency guards that check whether the source directory still exists and whether the target already contains merged artifacts. If a partial merge is detected, it warns you and stops instead of duplicating work.

The merge pauses and presents the conflicting fields side by side, requiring you to choose which convention the merged phase keeps. The decision is recorded in STATE.md with your rationale before the merge completes.

Avoid merging phases that are far apart in the roadmap, since the workflow warns when phases differ by more than two positions due to dependency risks. Also avoid merging when other phases depend solely on artifacts the source phase provides.