dependency-extract

Extract deliverable dependencies from source documents into a consumable Dependencies.csv by running a two-pass extraction that anchors relationships to project definitions and maps execution edges between deliverables.

A two-pass dependency extraction process first anchors relationships to the project definition, then maps execution edges between deliverables to ensure evidence-first provenance for governance and planning.

Generate a dependency register with evidence-first provenance by running extraction on a deliverable with a ready decomposition, producing canonical rows with proper TargetType handling and lifecycle fields.

Yes, you need a ready decomposition path before extracting dependencies, as the skill operates on a defined run root and decomposition path to produce per-deliverable dependency registers.

Extracting dependencies generates a v3.1 Dependencies.csv file and an accompanying _DEPENDENCIES.md file containing run notes and lifecycle data for downstream aggregation and reconciliation.

Dependency extraction validates enums and IDs to enforce canonical row formatting, ensure proper TargetType handling, and maintain accurate lifecycle fields for downstream reconciliation.