About dependency-graph
A skill for mapping blockers across batches of work items, including implicit dependencies caused by outputs, overlapping files, or decisions. It identifies the open items that can start and updates that frontier as work completes.
Key features
- 01Identify explicit and implicit blockers
- 02Check dependencies on deliverables
- 03Find overlapping file or module work
- 04Detect decision- and interface-dependent tasks
- 05Calculate the startable frontier
- 06Recompute the frontier after completion
Use cases
- 01Map ordering across a batch of work
- 02Find undeclared dependencies
- 03Determine which items can start in parallel
- 04Update blockers when work is completed
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/dependency-graphin Claude Code to confirm it loaded.
Details
From the project READMEGiven a batch of work items, map which block which. Look past the dependencies items declare outright — the ones that bite are implicit.
Blocking edges
Item B is blocked by item A when B's text says so, and also when
- B needs something A produces — code, infrastructure, or data,
- B and A touch overlapping files or modules — a collision, not an order; pick one to go first and treat the other as blocked by it, or
- B's requirements hinge on a decision or interface A will establish.
The frontier
The frontier is the set of still-open items with zero blockers — they can start now.
Recompute the frontier whenever an item completes.
Done when: every item is classified as frontier or blocked, and each blocked item names every item it waits on.