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/customer_roadmap_template.md
View on GitHub# What's Coming in [Year]
> This roadmap is directional and may change as we learn from customers.
> Items in "Exploring" are not commitments. Dates may shift.
---
## Shipping this quarter
Specific features available this quarter. Customer-benefit framing -- name what they get, not what we build.
**[Theme / feature name 1]**
[1-2 sentence customer-benefit description. Plain language. No internal team names. No version numbers.]
**[Theme / feature name 2]**
[1-2 sentence description.]
**[Theme / feature name 3]**
[1-2 sentence description.]
**[Theme / feature name 4]** (optional)
[1-2 sentence description.]
---
## In development -- later this year
Themes we are actively building toward but with no committed date.
**[Theme 1]**
[1-2 sentence customer-benefit description.]
**[Theme 2]**
[1-2 sentence description.]
**[Theme 3]**
[1-2 sentence description.]
**[Theme 4]** (optional)
[1-2 sentence description.]
---
## Exploring
Directions we are investigating; not commitments. Use language like "exploring", "experimenting", "researching."
**[Direction 1]**
We are exploring [the area]. [Optional: brief context on why this direction is interesting.]
**[Direction 2]**
[Description.]
---
## How to track
- Sign up for the [product] newsletter for monthly updates
- Visit the changelog at [URL] for what shipped
- Submit feedback at [URL]
---
> **Caveats (repeat at the bottom):**
> - This roadmap reflects current planning. We update it quarterly.
> - Items in "Exploring" may not ship.
> - Specific dates for items beyond "Shipping this quarter" are not promised.
**Last updated:** [Month YYYY]
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 |