Skill

Skill: shared-roadmap

Build a unified, multi-team delivery roadmap that surfaces dependencies, aligns timelines, and gives all stakeholders a single source of truth.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-cross-team-coordination

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Build a unified, multi-team delivery roadmap that surfaces dependencies, aligns timelines, and gives all stakeholders a single source of truth.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.0k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-brainstorming

11 files

Facilitates interactive brainstorming sessions using diverse creative techniques and ideation methods. Activates when users say 'help me brainstorm' or 'help me ideate'.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: shared-roadmap

Purpose

Build a unified, multi-team delivery roadmap that surfaces dependencies, aligns timelines, and gives all stakeholders a single source of truth.

When to Use

Multiple teams are shipping to a shared release
Stakeholders are getting conflicting roadmap information from different teams
Quarterly planning requires cross-team alignment

Framework: Shared Roadmap

Principle

One roadmap. Multiple team swim lanes. Shared milestones and dependencies visible to all.

Step 1 — Gather Inputs

Ask for:

Participating teams and their current sprint/release plans
Shared milestones (code freeze, UAT, release date)
Known cross-team dependencies

Step 2 — Roadmap Format

Quarterly View (Now / Next / Later)

Team	Now (This Quarter)	Next (Next Quarter)	Later (Future)
Team A	Feature X, Feature Y	Feature Z	Platform migration
Team B	API v2	Reporting dashboard	—
Team C	Infrastructure upgrade	—	Real-time pipeline

Milestone Overlay

Milestone	Date	Teams Involved
Code Freeze	Week 8	All
UAT	Week 9–10	Team A, Team B
Release v3.0	Week 11	All

Dependency Callouts

Team A's Feature X depends on Team B's API v2 (due Week 4)
Team C's infra upgrade must complete before Team B's Reporting Dashboard

Step 3 — Roadmap Health Check

Are all dependencies represented and dated?
Do all teams have realistic capacity for their roadmap items?
Are there timeline conflicts between teams?

Step 4 — Communication Cadence

Roadmap reviewed at:

Weekly: Dependency status only
Monthly: Full team sync with updates
Quarterly: Full roadmap refresh

Output Format

Shared roadmap table (Now/Next/Later per team)
Milestone overlay
Dependency callouts
Review cadence
Suggested next command: /dependency-map or /steering-deck