SkillA skill gives Relay a specialist method it can reuse on your work.Operations and finance
Low riskSecurity review passed

Dependency Map

Map the delivery dependencies of a project across teams, systems, vendors, and decision points, then call out the critical path.

Sample result

How it works

What Dependency Map does

Inventories every input a deliverable needs, classifies each link (finish-to-start, data, access, decision, external), assigns a provider owner and a needed-by date, computes earliest and latest dates and float, finds the critical and near-critical chains, flags uncommitted and cyclic dependencies, and ranks them by how much a slip would move the end date.

Use it when

Someone asks what depends on what, who is blocking whom, what the critical path is, which handoffs or decisions put a date at risk, or for a dependency map before planning or a launch review.

Use something else for

Scoring uncertain events as risks, for pricing a requested change, or for diagnosing a sprint burndown.

Inputs and results

What goes in, what comes back

  1. You give

    A short brief describing what you need

    Add a specialist method to the work.

  2. You get

    Dependency map, critical path analysis, handoff table and escalation asks

    The method guides the work with your files and context.

  3. You check

    The sources and open questions

    Review the output against your brief.

Questions and answers

Questions about Dependency Map

Updated Oct 20, 2026.

What does Dependency Map do?

Map the delivery dependencies of a project across teams, systems, vendors, and decision points, then call out the critical path. Inventories every input a deliverable needs, classifies each link (finish-to-start, data, access, decision, external), assigns a provider owner and a needed-by date, computes earliest and latest dates and float, finds the critical and near-critical chains, flags uncommitted and cyclic dependencies, and ranks them by how much a slip would move the end date. Use when someone asks what depends on what, who is blocking whom, what the critical path is, which handoffs or decisions put a date at risk, or for a dependency map before planning or a launch review. Do not use for scoring uncertain events as risks (use risk-register), for pricing a requested change (use scope-change-brief), or for diagnosing a sprint burndown (use burndown-diagnosis).

Who is Dependency Map for?

It is designed for project managers, program leads, delivery leads, product teams and operations managers.

What do I need to use it?

Nothing extra is needed. Sign in to Relay to run it with your own files and context.

What does Dependency Map produce?

Dependency map, critical path analysis, handoff table and escalation asks. Results come back with their sources and any open questions for you to check before anything is used.

How much does Dependency Map cost?

It is free to use. Paid model usage, if any, is shown before a run.

Can an AI agent use it?

Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.

Details

Trust, access and technical details

Trust and access

Visibility
Public: anyone can view
Status
Published and maintained
Pricing
Free
Low riskSecurity review passedEvaluation suite validated
Reviewed version
cmvgt7lhk0045…
Reviewed
Oct 20, 2026
Static signals
0 signals
Source provenance
Commit pinned

Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.

Use it from code or an agent

Read the public definition, then check cost and inputs with a preflight before a run.

Open definition

POST /api/v1/runs/preflight

How agents connect to Relay →

Have a task this would help with?

Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.

Loading request box