pm-dependencies

Map task dependencies into a Directed Acyclic Graph and compute the critical path.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill pm-dependencies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-dependencies
Source: https://github.com/mahg-es/araya/tree/main/skills/pm-dependencies
Command: npx skills add https://github.com/mahg-es/araya --skill pm-dependencies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map task dependencies into a Directed Acyclic Graph (DAG) to reveal the correct sequencing of work and prevent deadlocks caused by circular or poorly ordered tasks.

Core Features & Use Cases

  • Build a dependency graph from backlog items and decomposed tasks.
  • Detect cycles and identify the critical path to reveal bottlenecks.
  • Output a dependencies artifact at .araya/plan/spec/dependencies.md for planning and execution tracking.

Quick Start

Feed your decomposed backlog into the skill and run it to produce the dependencies graph and critical path output.

Frequently Asked Questions about pm-dependencies

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

FAQPage Schema
How do I map task dependencies into a DAG for sprint planning?

A critical path is the longest sequence of dependent tasks in a DAG, determining the minimum project duration. Computing the critical path highlights bottlenecks and risks by identifying tasks that cannot be delayed without extending the overall timeline.

How do I detect circular dependencies in a project backlog?

You can detect circular dependencies by mapping your backlog into a Directed Acyclic Graph, which enforces DAG integrity by rejecting cycles. This prevents deadlocks caused by poorly ordered tasks during backlog grooming and risk assessment.

Can I use a dependency graph for risk analysis and bottleneck identification?

Yes, you can use a dependency graph for risk analysis by computing the critical path to identify bottlenecks. Mapping task dependencies reveals the true sequence of work, highlighting tasks that pose schedule risks to the overall project plan.

What format does the dependencies artifact output use for execution tracking?

The dependencies artifact outputs as a markdown file at .araya/plan/spec/dependencies.md. This file captures the dependency graph and critical path, providing a reference for planning, risk assessment, and execution tracking.

Do I need to decompose backlog items before mapping task dependencies?

Yes, you need to decompose backlog items into discrete tasks before mapping task dependencies. The tool builds the dependency graph from decomposed tasks to accurately sequence work and identify the critical path.