Deps Skill - Dependency Analysis

You are an expert at analyzing and visualizing software project dependencies.

When to Use

Use this skill when:

•Understanding what's blocking an issue
•Planning work order
•Identifying circular dependencies
•Finding critical path items

Process

•

Visualize Dependencies

bash

linear deps ENG-100
linear deps --team ENG

•
Analyze Blocking Chains
- •Find longest blocking chains
- •Identify bottleneck issues
- •Locate circular dependencies
•
Recommend Actions

Dependency Types

Type	Meaning	Example
blocks	A must complete before B	Auth blocks Login UI
blocked_by	B cannot start until A done	Login UI blocked by Auth
related	Informational link	Two related features
duplicate	Same issue	Close one, reference other

Visualization Output

code

DEPENDENCY GRAPH: ENG-100
════════════════════════════════════════
ENG-100 User Authentication Epic
├─ ENG-101 Login flow [In Progress]
│  ├─ ENG-103 OAuth integration [Todo]
│  │     → blocks: ENG-105
│  └─ ENG-104 Session management [Todo]
├─ ENG-102 Logout flow [Blocked]
│     ← blocked by: ENG-101
└─ ENG-105 Token refresh [Blocked]
      ← blocked by: ENG-103
────────────────────────────────────────
5 issues, 4 dependencies, 0 cycles

Analysis Areas

Blocking Chains

Issues that block many other issues are critical:

code

Critical blocker: ENG-101
  → blocks 3 issues directly
  → blocks 5 issues transitively

Circular Dependencies

Cycles prevent any issue from completing:

code

⚠ Circular dependency detected:
  ENG-201 → ENG-202 → ENG-203 → ENG-201

Critical Path

Longest dependency chain determines minimum completion time:

code

Critical path (4 issues):
  ENG-100 → ENG-101 → ENG-103 → ENG-105
Minimum time: 4 issue completion times

Orphaned Dependencies

Issues referencing non-existent or closed issues:

code

⚠ Orphaned dependencies:
  ENG-150 blocked by ENG-099 (closed)

Commands Used

bash

# Single issue dependencies
linear deps ENG-100

# Team-wide dependencies
linear deps --team ENG

# Check what blocks an issue
linear issues blocked-by ENG-100

# Check what an issue blocks
linear issues blocking ENG-100

# Create a dependency
linear issues update ENG-102 --blocked-by ENG-101

# Remove a dependency (update with empty)
linear issues update ENG-102 --blocked-by ""

Discovery Commands (NEW)

Use search to discover dependency-related issues:

bash

# Find all blocked issues (useful for prioritizing unblocking work)
linear search --has-blockers --team ENG

# Find issues blocked by a specific issue
linear search --blocked-by ENG-100

# Find issues blocking a specific issue
linear search --blocks ENG-100

# Find circular dependencies
linear search --has-circular-deps --team ENG

# Find complex dependency chains
linear search --max-depth 5 --team ENG

Pro tip: Use /link-deps skill to discover and establish missing dependencies across your backlog.

Action Recommendations

Based on analysis, recommend:

•Unblock critical path - Prioritize blockers
•Break cycles - Remove unnecessary dependencies
•Parallelize - Find work that can happen concurrently
•Update stale deps - Clean up outdated relationships

Best Practices

•Keep dependencies minimal - Only add necessary ones
•Use blocks, not blocked_by - Clearer mental model
•Review regularly - Dependencies become stale
•Document non-obvious deps - Add comments explaining why