cross-project-dependency-map

name	cross-project-dependency-map
description	Maintain a dependency map across projects/repos/teams using prerequisite outcomes, interfaces, needed-by dates, owners, readiness evidence, and failure consequences.

Cross Project Dependency Map

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using project plans, technical contracts, release schedules, staffing/capacity, and milestones. Do not fill material gaps with assumptions when they can change the result.
3. Represent dependencies as required deliverables not vague relationships, identify critical path and fan-in points, validate owner commitments, and update on evidence changes.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

A blocked or slipping dependency is visible before it surprises the consuming workstream.