How do I install the Team Dependency skill?

Run npx skillmds@latest add majiayu000/team-dependency in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Team Dependency skill do?

Map and visualize dependencies between features and work items. It is listed under Coding & Dev Tools on SkillMD.

Is Team Dependency safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Team Dependency?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Team Dependency free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Team Dependency?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Team Dependency by majiayu000 — Agent Skill

Name: Team Dependency
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

name: team-dependency description: "[Team] 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"." argument-hint: "[pbi-file|feature-name|all]" infer: true allowed-tools: Read, Write, Edit, Grep, Glob, TodoWrite

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

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

Dependency Types

Type	Symbol	Description
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

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

Example

/team-dependency team-artifacts/pbis/260119-pbi-dark-mode-toggle.md
/team-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

---name: team-dependencydescription: Map and visualize dependencies between features and work items.--- --- name: team-dependency description: "[Team] 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"." argument-hint: "[pbi-file|feature-name|all]" infer: true allowed-tools: Read, Write, Edit, Grep, Glob, TodoWrite --- # 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 | Type | Symbol | Description | | ---------- | ------ | ----------------------------------- | | 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 ```markdown ## 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:** `/team-dependency` ## Example ```bash /team-dependency team-artifacts/pbis/260119-pbi-dark-mode-toggle.md /team-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

Frequently asked questions

Team Dependency