borghei/Claude-Skills / project-management/execution/roadmap-communication
roadmap-communication
VerifiedProduce executive, customer and internal versions of one roadmap with consistent framing and the right detail and risk language for each. Use when publishing the quarterly roadmap, a board packet or a customer or sales roadmap.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.9 KB |
| assets/customer_roadmap_template.md | markdown | 1.6 KB |
| assets/executive_roadmap_template.md | markdown | 2.2 KB |
| assets/internal_roadmap_template.md | markdown | 3.9 KB |
| examples/pylon-roadmap-three-ways.md | markdown | 10.4 KB |
| references/red-flags.md | markdown | 10.6 KB |
| references/roadmap-communication-guide.md | markdown | 10.4 KB |
| references/roadmap-variants-playbook.md | markdown | 10.9 KB |
assets/internal_roadmap_template.md
View on GitHub# [Product / Team] -- [Quarter] Roadmap (Internal)
**Strategy:** [One sentence -- the strategic bet this quarter advances]
**NSM:** [Link to NSM spec]
**OKRs:** [Link to quarterly OKR doc]
**Sponsor:** [Exec sponsor]
**Last updated:** [YYYY-MM-DD]
**Distribution:** [Internal teams only -- engineering, design, support, account, leadership]
> **Source of truth.** This document is the canonical roadmap. The executive and customer variants are derived from this.
---
## Now ([current quarter]) -- features in flight or starting imminently
| ID | Feature | Outcome it serves | PM | EM | Design | Status | Target sprint / release | KR mapped | Dependencies | Risks |
|----|---------|-------------------|----|----|--------|--------|------------------------|-----------|--------------|-------|
| F-101 | [Feature name] | [Outcome it ladders up to] | [Name] | [Name] | [Name] | [Discovery / In flight / In review / Done] | [Sprint NN / Release date] | [KR1] | [List or "None"] | [Risk + mitigation, or "None"] |
| F-102 | [Feature name] | [Outcome] | [Name] | [Name] | [Name] | [Status] | [Target] | [KR] | [Deps] | [Risks] |
| F-103 | [Feature name] | [Outcome] | [Name] | [Name] | [Name] | [Status] | [Target] | [KR] | [Deps] | [Risks] |
| F-104 | [Feature name] | [Outcome] | [Name] | [Name] | [Name] | [Status] | [Target] | [KR] | [Deps] | [Risks] |
| F-105 | [Feature name] | [Outcome] | [Name] | [Name] | [Name] | [Status] | [Target] | [KR] | [Deps] | [Risks] |
---
## Next ([next 1-2 quarters]) -- themes and candidate features
| Theme | Outcome | Candidate features | PM | EM | Target quarter | Expected dependencies | Open questions |
|-------|---------|--------------------|----|----|----------------|----------------------|----------------|
| [Theme name] | [Outcome] | [F-201 candidate; F-202 candidate] | [Name] | [Name] | [Q] | [Deps] | [Questions still open] |
| [Theme name] | [Outcome] | [Candidates] | [Name] | [Name] | [Q] | [Deps] | [Questions] |
| [Theme name] | [Outcome] | [Candidates] | [Name] | [Name] | [Q] | [Deps] | [Questions] |
---
## Later ([H2 or beyond]) -- directions and hypotheses
| Direction | Hypothesis | Sponsor | What we'd need to be true to commit |
|-----------|------------|---------|-------------------------------------|
| [Direction] | [The bet, stated as a testable hypothesis] | [Exec sponsor] | [List of assumptions or experiments that would move this to Next/Now] |
| [Direction] | [Hypothesis] | [Sponsor] | [Conditions] |
---
## Cross-cutting dependencies
| Dependency | Owner | Needed by | Status |
|------------|-------|-----------|--------|
| [Platform change / infra / vendor work] | [Team or vendor] | [F-101 needs by 2026-06-12] | [On track / At risk / Blocked] |
---
## Capacity view (per quarter)
| Team | Committed (story points or eng-weeks) | Available capacity | Utilization | Notes |
|------|---------------------------------------|--------------------|-------------|-------|
| [Team A] | [N] | [M] | [%] | [Notes on hiring, holidays, on-call] |
| [Team B] | [N] | [M] | [%] | [Notes] |
> Target utilization: 70-80%. Above 90% means no buffer for incidents/spikes; below 60% means underloaded or padded.
---
## Trace to other artifacts
- **PRDs (`create-prd/`):** F-101 -> [link], F-102 -> [link], ...
- **PR/FAQs (`prfaq/`):** F-101 -> [link if applicable]
- **OKRs:** [link to quarterly OKR doc]
- **NSM spec:** [link]
- **Dependency map (`dependency-map/`):** [link if used]
---
## Distribution log
| Date | Variant published | Distributed to |
|------|-------------------|---------------|
| [YYYY-MM-DD] | Internal | Engineering, design, support, account, leadership |
| [YYYY-MM-DD] | Executive | Board, exec team |
| [YYYY-MM-DD] | Customer | Public site, sales decks |
---
## Change log
| Date | Change | Reason | Communicated to |
|------|--------|--------|----------------|
| [YYYY-MM-DD] | [Item added / removed / re-sequenced] | [Reason] | [Audiences notified] |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |