gsd-analyze-dependencies

To analyze project phase dependencies for a milestone roadmap, evaluate file overlap, semantic API dependencies, and data flow between phases to detect ordering constraints. This ensures parallel work conflicts are surfaced before roadmap planning.

A phase dependency graph in project management maps ordering constraints between phases by tracking file overlap and data flow. It identifies when one phase consumes outputs from another, dictating the correct execution sequence.

To format 'Depends on' entries in a ROADMAP.md file, map analyzed phase ordering constraints directly to the roadmap. Explicitly declare that a consuming phase depends on its producing phase to ensure correct sequencing and prevent conflicts.

Parallel work causes conflicts across project phases when file overlap and data flow dependencies are unmapped. If a downstream phase consumes APIs from an upstream phase without ordering constraints, execution sequencing breaks.

Yes, you can detect semantic API dependencies between project phases by analyzing the phase dependency graph. This evaluates API usage and data flow to propose explicit 'Depends on' relationships for your roadmap.