OpenParable
Skip to content
← Back to skills

Dependency

Productivity
dependency

Dependency is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Map and visualize feature dependencies. Use when analyzing dependencies, identifying blockers, or creating dependency graphs. Triggers on keywords like "dependencies", "blockers", "what blocks", "dependency map".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/dependency/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dependency, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Dependency Mapping

Map and visualize dependencies between features and work items.

When to Use

  • Planning feature sequencing
  • Identifying blockers
  • Understanding critical path

Pre-Workflow

Activate Skills

  • Activate project-manager skill for dependency analysis best practices

Quick Reference

Workflow

  1. Read target PBI/feature or all items from team-artifacts/pbis/
  2. Extract dependency fields
  3. Build dependency graph
  4. Identify risks (circular dependencies, unresolved blockers, external dependencies)
  5. Identify critical path
  6. Generate visualization report
  7. Output to console or save to file

Dependency Types

TypeSymbolDescription
Blocked by->Cannot start until X completes
Blocks<-X cannot start until this completes
Mutual<->Bidirectional dependency
Related to=>Shares code/design elements
Depends on~>Needs external (API, service)

Graph Notation

Feature A -> Feature B (blocked by)
Feature A <- Feature C (blocks)
Feature A <-> Feature D (mutual)

Visualization Template

## Dependency Map

### {Feature}

**Upstream (We depend on):**
- [ ] {Dep 1} - {status}
- [ ] {Dep 2} - {status}

**Downstream (Depends on us):**
- [ ] {Dep 1} - {their deadline}

### Critical Path
{A} -> {B} -> {C} -> {D}

### Risk Areas
- Red: {Feature X} blocking 3 items
- Yellow: {External API} - timeline uncertain

Output Format

A -> B -> C (critical path)
     \-> D

Legend:
-> blocks
=> related

Related

  • Role Skill: project-manager
  • Command: /dependency

Example

/dependency team-artifacts/pbis/260119-pbi-dark-mode-toggle.md
/dependency all

IMPORTANT Task Planning Notes

  • Always plan and break many small todo tasks
  • Always add a final review todo task to review the works done at the end to find any fix or enhancement needed