From pdm-agile-delivery
Classify, assign, and track delivery blockers systematically — so they are resolved quickly and don't accumulate silently.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-agile-delivery:blocker-triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Classify, assign, and track delivery blockers systematically — so they are resolved quickly and don't accumulate silently.
Classify, assign, and track delivery blockers systematically — so they are resolved quickly and don't accumulate silently.
| Type | Definition | Resolution Owner |
|---|---|---|
| Technical | Code, environment, or tooling issue | Tech Lead / Dev |
| Dependency | Waiting on another team's output | PDM (cross-team) |
| Decision | Needs a call that hasn't been made | Accountable party |
| Resource | Missing skill, person, or access | PDM / Manager |
| External | Vendor, legal, third-party | PDM / Escalate |
| Severity | Impact | SLA to Resolve |
|---|---|---|
| 🔴 Critical | Stops sprint goal | Same day |
| 🟡 High | Slows 2+ team members | 24 hours |
| 🟢 Medium | Slows 1 person | 48 hours |
| # | Description | Type | Severity | Raised By | Owner | Raised Date | Target Resolution | Status |
|---|---|---|---|---|---|---|---|---|
| B1 | API docs unavailable from vendor | External | 🔴 | Dev | PDM | [date] | [date] | 🔄 In Progress |
If a blocker is:
/sprint-health or /escalation-frameworknpx claudepluginhub devmuslim/pdm-skills --plugin pdm-agile-deliveryTriages Jira issues by classifying type, assessing complexity (0-100 scale), determining priority/severity, and routing to workflows/agents.
Scans project email threads to identify blockers, dependencies, and impediments preventing progress. Useful for project managers or team leads querying 'what's blocking the project'.
Structures escalations in /do workflow for blocking Global Invariants, Acceptance Criteria, and manual reviews with evidence, attempts, hypotheses, and resolution options.