dependency

• Planning feature sequencing
• Identifying blockers
• Understanding critical path

Activate Skills

• Activate project-manager skill for dependency analysis best practices

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)

```

```markdown

{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

```bash

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

/dependency all

```

• 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