From pdm-cross-team-coordination
Facilitate structured resolution of cross-team priority conflicts using a neutral, data-driven framework. Helps PDMs broker agreement without escalating to leadership unnecessarily.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-cross-team-coordination:conflict-resolutionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Facilitate structured resolution of cross-team priority conflicts using a neutral, data-driven framework. Helps PDMs broker agreement without escalating to leadership unnecessarily.
Facilitate structured resolution of cross-team priority conflicts using a neutral, data-driven framework. Helps PDMs broker agreement without escalating to leadership unnecessarily.
"Separate positions from interests. Teams argue over positions ('We need this in Sprint 15') but share interests ('We both want the release to succeed'). Find the shared interest."
Ask:
| Team | Position (What they say) | Interest (Why they want it) |
|---|---|---|
| Team A | Need feature X in Sprint 15 | Customer demo on March 10 |
| Team B | Can't deliver X until Sprint 17 | Current focus on Platform stability |
For each option, assess:
Brainstorm 3–4 resolution options:
Score each option:
| Option | Business Value | Feasibility | Risk | Relationship Impact | Score |
|---|---|---|---|---|---|
| Option 1 | 3 | 1 | 3 | 2 | 9 |
| Option 2 | 1 | 3 | 1 | 2 | 7 |
| Option 3 | 2 | 2 | 2 | 3 | 9 |
State the recommended option with rationale. Draft a one-paragraph summary suitable for sharing with both teams.
If no resolution is possible at this level, define:
/decision-log or /status-updatenpx claudepluginhub devmuslim/pdm-skills --plugin pdm-cross-team-coordinationCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.