qsd-analyze-dependencies

You detect missing roadmap dependencies by inspecting file overlaps and API-level semantic links across phases. This analysis infers ordering constraints and outputs concrete ROADMAP.md updates encoded as Depends on entries to align execution order.

Finding missing Depends on entries for overlapping file edits involves analyzing the phase dependency graph to identify ordering constraints. It detects semantic dependencies where one phase consumes outputs from another and suggests concrete ROADMAP.md updates to prevent parallel drift.

Updating ROADMAP.md to reflect data-output-driven workflow ordering constraints requires analyzing phase dependencies to validate execution order. The analysis generates precise ROADMAP.md edits encoded as Depends on entries to ensure structural validity against the milestone.

Detecting API-level semantic dependencies between roadmap milestones is possible by analyzing the phase dependency graph. The process identifies ordering constraints where one phase consumes outputs from another and suggests concrete ROADMAP.md updates to reflect required dependencies.

You need to analyze milestone dependencies before starting manager execution when phases have overlapping file edits or data-output-driven workflows. Running dependency analysis fills missing Depends on entries in ROADMAP.md to prevent parallel drift and merge conflicts.