gsd-analyze-dependencies

Analyzing phase dependencies identifies overlapping file modifications and semantic API usage to prevent merge conflicts. The tool ranks dependencies and proposes explicit Depends on entries for your ROADMAP.md to ensure correct execution ordering.

Adding Depends on relationships to ROADMAP.md is best handled by running an analyze-dependencies workflow. It automatically detects data flow and file overlaps between milestone phases to populate missing fields and propose necessary ordering updates.

You need to analyze milestone phase dependencies when multiple development phases run in parallel. This process detects overlapping file edits and semantic API dependencies, allowing you to establish explicit ordering rules and prevent execution conflicts.

Yes, you can use this to fix missing dependency entries in ROADMAP.md. It examines data flow between milestone phases, ranks dependencies based on file overlaps and API usage, and applies the required Depends on updates directly to your roadmap.

This dependency analysis requires access to the milestone's ROADMAP.md file to function correctly. It uses the analyze-dependencies workflow to parse existing phase graphs, identify missing fields, and apply the necessary dependency updates.

Phase dependencies are ranked during conflict resolution by examining overlapping file modifications, semantic API dependencies, and data flow between phases. The analysis uses these metrics to propose explicit Depends on entries and prevent parallel execution conflicts.