agentsclimarketplace

Dependency mapping

Skill janellecipriano/pm-skills/skills/dependency-mapping

Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.

Install
npx -y skills add janellecipriano/pm-skills --skill dependency-mapping

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Map cross-team and external dependencies for a project — what's needed, from whom, by when — and identify the critical path and at-risk handoffs. Use when the user says "map dependencies", "what are we blocked on", "cross-team dependencies", "critical path", or needs to coordinate handoffs across teams or vendors.

SKILL.md

2.0 KB, as published. Nobody here has run it

Dependency Mapping

Make every cross-team and external dependency visible, owned, and dated — and surface the ones that threaten the timeline.

When to use

  • Coordinating delivery that spans multiple teams or vendors.
  • Diagnosing what's blocking progress or building a dependency view for a plan/review.

Inputs to gather

  • The deliverables/milestones and their target dates.
  • For each: what's needed from another team/vendor, and what others need from you.
  • Known owners on both sides and any commitments already made.

Process

  1. List dependencies as directional edges: A needs X from B by date D.
  2. For each, capture: provider, consumer, what, needed-by date, provider's committed date, status, and owner.
  3. Flag a dependency at risk when there's no committed date, the committed date is after needed-by, or the owner is unconfirmed.
  4. Identify the critical path — the chain of dependencies that, if any slips, slips the whole project.
  5. Note circular/mutual dependencies and sequencing conflicts explicitly.
  6. Recommend actions: confirm owners, get commitments, decouple where possible, add buffer.

Output format

## Dependency Map — {{project}}

| ID | What | Provider → Consumer | Needed by | Committed | Status | Owner | At risk? |
| --- | --- | --- | --- | --- | --- | --- | --- |

### Critical path
{{ordered chain with dates}}

### At-risk dependencies & recommended actions
- {{dependency}} — {{why at risk}} → {{action, owner, by when}}

If a visual helps, offer a simple text/Mermaid dependency diagram.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.