gpd-merge-phases

To automate merging research phases, you can use a skill that absorbs one phase into another by validating phase existence, updating project documentation, and handling dependencies automatically.

Consolidating data and plans involves combining results and artifacts from a source phase into a target phase, which simultaneously updates the project roadmap, summaries, and state files.

Yes, merging research phases requires a project context with a specific file structure and defined project state to ensure dependencies and documentation are updated correctly.

The best way to update documentation when combining phases is to automate the workflow, ensuring the project roadmap and state files absorb the source phase's plans and verification results seamlessly.

Yes, you can merge dependencies and verification results by executing a series of automated steps that absorb the source phase's artifacts and update the target phase's project state.