From pdm-release-planning
Map all delivery dependencies — between teams, systems, and external parties — to surface the critical path and flag risks before they become blockers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-release-planning:dependency-mapThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Map all delivery dependencies — between teams, systems, and external parties — to surface the critical path and flag risks before they become blockers.
Map all delivery dependencies — between teams, systems, and external parties — to surface the critical path and flag risks before they become blockers.
Ask for:
| Type | Definition | Example |
|---|---|---|
| Technical | Code or API dependency between teams | Backend API needed by Mobile |
| Data | Data or schema dependency | Data team migration needed before Backend |
| Infrastructure | Shared infra dependency | DevOps environment needed by QA |
| External | Outside the organization | App Store review, vendor API |
| Approval | Sign-off or gate required | Legal, Compliance, Business UAT |
| # | From | To | Type | Description | Due Date | Risk Level |
|---|---|---|---|---|---|---|
| D1 | Backend | Mobile | Technical | WebSocket API contract finalized | Week 2 | 🔴 High |
| D2 | DevOps | QA | Infrastructure | Staging env with production data | Week 3 | 🟡 Medium |
| D3 | Mobile | Apple | External | App Store review submission | Week 4 | 🔴 High |
| D4 | QA | Business | Approval | UAT sign-off | Week 5 | 🟡 Medium |
Identify the sequence of dependencies that determines the earliest possible release date.
Critical Path: D1 → D3 → D4
Earliest release date based on critical path: [calculated date]
/risk-register or /plan-releasenpx claudepluginhub devmuslim/pdm-skills --plugin pdm-release-planningIdentify and visualize dependencies between teams, systems, and work items to prevent blocked work. Use when planning cross-team initiatives.
Builds milestone plans that are dependency-aware, risk-aware, and tied to delivery outcomes. Use when entering production, scope changes, or needing a realistic plan.
Computes critical path, blocked tasks, and cycles from task dependencies. Read-only analysis until the user asks to reorder.