From pdm-cross-team-coordination
Build a structured integration plan for features or systems spanning multiple teams — with clear interfaces, milestones, testing strategy, and escalation paths.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pdm-cross-team-coordination:integration-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build a structured integration plan for features or systems spanning multiple teams — with clear interfaces, milestones, testing strategy, and escalation paths.
Build a structured integration plan for features or systems spanning multiple teams — with clear interfaces, milestones, testing strategy, and escalation paths.
| Interface | Provider Team | Consumer Team | Type | Contract Format | Due Date |
|---|---|---|---|---|---|
| Payment API v2 | Payments | Checkout | REST API | OpenAPI spec | Week 2 |
| User events stream | Platform | Analytics | Kafka | Avro schema | Week 3 |
| Feature flags | DevOps | All teams | SDK | Documentation | Week 1 |
| Milestone | Date | Owner | Done When |
|---|---|---|---|
| API contract agreed | Week 1 | Tech Leads | Both teams sign off on spec |
| Mock server available | Week 2 | Provider | Consumer can test against mock |
| Integration in staging | Week 3 | Both teams | E2E test passes in staging |
| Integration testing complete | Week 4 | QA | No P0/P1 integration bugs |
| Production ready | Week 5 | PDM | All gates passed |
If integration is blocked:
/dependency-map or /sync-meetingnpx 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.