dependency-graph

Generate Mermaid dependency graphs with criticality analysis and single-point-of-failure detection.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jp5labs/forge-workflow --skill dependency-graph-jp5labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-graph
Source: https://github.com/jp5labs/forge-workflow/tree/main/forge_workflow/templates/skills/dependency-graph
Command: npx skills add https://github.com/jp5labs/forge-workflow --skill dependency-graph-jp5labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding how systems connect and where failures cascade is difficult when architecture knowledge is scattered across docs and tribal knowledge. This Skill maps upstream and downstream dependencies into a visual diagram so you can assess blast radius before making changes. ## Core Features & Use Cases - Dependency Mapping: Extracts upstream and downstream relationships from architecture docs, ADRs, and integration notes, capturing protocol, pattern, and data flow for each connection. - Risk Analysis: Identifies critical paths, single points of failure, circular dependencies, and high fan-in/fan-out hub systems. - Colour-Coded Mermaid Diagrams: Produces flowcharts with nodes styled by criticality (critical, high, medium, low, external) and edges showing sync vs. async patterns. - Use Case: Before modifying OrderService, run the skill to see which systems depend on it, discover that PaymentGateway has no failover, and get recommendations to add redundancy before deploying changes. ## Quick Start Ask the AI to generate a dependency graph for OrderService showing both upstream and downstream systems two hops deep.

Frequently Asked Questions about dependency-graph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I visualize system dependencies in a Mermaid diagram?

Invoke the skill with a system name and optional direction and depth parameters, such as /dependency-graph OrderService --direction both --depth 2. It reads architecture docs and integration notes, then outputs a Mermaid flowchart with colour-coded criticality.

How to find single points of failure in a system architecture?

The skill analyzes fan-in counts and failover status for each system, then lists systems that many others depend on without redundancy. Results appear in a dedicated Single Points of Failure table with risk levels.

What information does the dependency graph need to work?

It searches existing architecture notes, ADRs, and integration documentation for mentions of the target system. It extracts source, target, protocol, integration pattern, criticality, and data flow for each connection it finds.

Can I filter the dependency graph by criticality or domain?

Yes, use the --filter parameter with domain, team, or criticality values. For example, --filter criticality shows only critical and high-importance dependency chains, and --depth controls how many hops to traverse.

Does the dependency graph detect circular dependencies?

Yes, the analysis phase detects systems that directly or indirectly depend on each other. Circular dependencies are reported in a dedicated table with associated risks such as deadlock during failures.