dependencies

Detect and classify dependencies between approved user stories, generating a Mermaid graph and relationship table.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/686f6c61/PSPO-Agent --skill dependencies-686f6c61
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependencies
Source: https://github.com/686f6c61/PSPO-Agent/tree/main/skills/dependencies
Command: npx skills add https://github.com/686f6c61/PSPO-Agent --skill dependencies-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill makes hidden dependencies and potential blockers between product stories visible, preventing delays and ensuring smoother project execution.

Core Features & Use Cases

  • Dependency Detection: Identifies technical, data, flow, UX, and operational dependencies between approved user stories.
  • Confirmation & Classification: Distinguishes between confirmed and inferred dependencies, highlighting critical paths.
  • Impact Analysis: Shows which individuals are impacted if a key story is delayed and outlines necessary completion chains.
  • Use Case: After defining your user stories and assigning them, run this skill to visualize which stories must be completed before others can start, and who will be affected by any delays.

Quick Start

Run the dependencies skill to generate an operational map of story dependencies.

Frequently Asked Questions about dependencies

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

FAQPage Schema
How do I map dependencies and blockers between user stories?

Map story dependencies by analyzing approved user stories to detect technical, data, flow, UX, and operational blockers. This generates a markdown file with a Mermaid graph and relationship table highlighting critical paths and potential delays.

What is the best way to visualize project blockers and assigned personnel impact?

Visualize project blockers by generating a Mermaid graph and relationship table in a markdown file. This map outlines operational impacts on assigned individuals, showing exactly who is affected if a key user story is delayed.

How do I classify inferred and confirmed dependencies in project management?

Classify inferred and confirmed dependencies by analyzing approved user stories across technical, data, flow, UX, and operational categories. This distinction proactively manages project risks by highlighting critical paths versus potential assumptions.

Do I need approved user stories before tracking technical and UX dependencies?

Yes, you need approved user stories before tracking dependencies. The analysis detects relationships and blockers between stories that have already been defined and assigned to generate an accurate operational impact map.

Why does dependency mapping generate a Mermaid graph and markdown file?

Dependency mapping generates a Mermaid graph and markdown file to visually document technical, data, flow, UX, and operational relationships. This provides a clear relationship table and highlights operational impacts on assigned personnel.

When should I not use automated dependency detection for user stories?

Avoid automated dependency detection when user stories are not yet approved or assigned. The analysis relies on defined stories to accurately infer and confirm operational impacts, technical blockers, and completion chains.