메뉴
Visualize and analyze issue dependencies in Linear. Finds blocking chains, circular dependencies, and critical path items.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Triage and prioritize Linear backlog issues using the linear CLI. Analyzes staleness, blockers, dependency health, and priority mismatches. Use when the user asks about backlog grooming, sprint planning, issue prioritization, managing stale tickets, or cleaning up Linear issues.
Pre-release checklist to ensure CHANGELOG, version numbers, tests, and documentation are updated before cutting a release.
Discover and link related issues as dependencies. Searches for issues that should be connected and recommends dependency relationships to establish proper work order.
Create agent-friendly Linear tickets with PRDs, sub-issues, and clear success criteria. Use when planning features or breaking down work for agentic coding.
Triage and prioritize Linear backlog. Analyzes issues for staleness, blockers, and suggests priorities based on dependencies and capacity.
Plan Linear cycles using velocity analytics. Suggests scope based on historical capacity, identifies dependency risks, balances workload.
SOC 직업 분류 기준
| name | deps |
| description | Visualize and analyze issue dependencies in Linear. Finds blocking chains, circular dependencies, and critical path items. |
You are an expert at analyzing and visualizing software project dependencies.
Use this skill when:
Visualize Dependencies
linear deps ENG-100
linear deps --team ENG
Analyze Blocking Chains
Recommend Actions
| 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 |
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
Issues that block many other issues are critical:
Critical blocker: ENG-101
→ blocks 3 issues directly
→ blocks 5 issues transitively
Cycles prevent any issue from completing:
⚠ Circular dependency detected:
ENG-201 → ENG-202 → ENG-203 → ENG-201
Longest dependency chain determines minimum completion time:
Critical path (4 issues):
ENG-100 → ENG-101 → ENG-103 → ENG-105
Minimum time: 4 issue completion times
Issues referencing non-existent or closed issues:
⚠ Orphaned dependencies:
ENG-150 blocked by ENG-099 (closed)
# 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 ""
Use search to discover dependency-related issues:
# 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.
Based on analysis, recommend: