gsd-analyze-dependencies

To analyze milestone phase dependencies, you inspect the current milestone and reference ROADMAP.md to identify file overlap, API usage, and data-flow links across phases. This process proposes proper Depends on relationships to resolve execution order conflicts.

You should update Depends on entries in ROADMAP.md during milestone planning to avoid parallel conflict and misalignment. Identifying cross-phase dependencies at this stage ensures dependent phases are properly ordered and tracked before execution begins.

The best way to resolve cross-phase dependencies in milestone planning is to analyze the milestone dependency graph to determine required execution order. This allows you to suggest precise ROADMAP.md updates for Depends on entries, preventing phase misalignment.

You prevent parallel conflicts between roadmap phases by analyzing milestone dependencies to map file overlap and data-flow links. Applying confirmed dependency updates to ROADMAP.md ensures phases with execution dependencies are correctly ordered.

You can automate ROADMAP.md dependency updates by running an end-to-end analysis that inspects the current milestone and applies confirmed dependency updates. This identifies data-flow links and file overlap to propose precise Depends on entries.

Milestone planning fails due to incorrect phase ordering when cross-phase dependencies like file overlap and API usage are not mapped. Analyzing milestone dependencies and updating ROADMAP.md with correct Depends on entries resolves this misalignment.