product-roadmap-how-to-communicate-changes
Sub-skill of product-roadmap: How to Communicate Changes (+1).
Best use case
product-roadmap-how-to-communicate-changes is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of product-roadmap: How to Communicate Changes (+1).
Teams using product-roadmap-how-to-communicate-changes should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/how-to-communicate-changes/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How product-roadmap-how-to-communicate-changes Compares
| Feature / Agent | product-roadmap-how-to-communicate-changes | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of product-roadmap: How to Communicate Changes (+1).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# How to Communicate Changes (+1) ## How to Communicate Changes 1. **Acknowledge the change**: Be direct about what is changing and why 2. **Explain the reason**: What new information drove this decision? 3. **Show the tradeoff**: What was deprioritized to make room? 4. **Show the new plan**: Updated roadmap with the changes reflected 5. **Acknowledge impact**: Who is affected and how? ## Avoiding Roadmap Whiplash - Do not change the roadmap for every piece of new information - Batch roadmap updates at natural cadences (monthly, quarterly) - Distinguish between "roadmap change" (strategic reprioritization) and "scope adjustment" (normal execution refinement) - Track how often the roadmap changes
Related Skills
well-production-dashboard
Create interactive well production dashboards with real-time monitoring, verification integration, economic metrics, and multi-format exports. Use for well performance analysis, field aggregation, production forecasting, and API-driven dashboards.
production-forecaster
Forecast oil & gas well production using decline curve analysis. Use when estimating EUR, generating type curves, fitting Arps models (exponential, hyperbolic, harmonic), or running reserve calculations. Supports conventional and unconventional wells, P10/P50/P90 probabilistic outputs, and multi-field type curve comparison.
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
cli-productivity
Essential CLI tools and shell productivity patterns for efficient terminal workflows
github-roadmap-anchor-reuse
Reuse and reopen existing roadmap/epic GitHub issues instead of fragmenting work across duplicate replacement epics; retarget children and link active issues for continuity.
domain-gap-to-issue-roadmap
Deep multi-repo ecosystem audit → domain gap matrix → structured GitHub issue roadmap with epics. Use when the user wants to assess capabilities across repos and create a backlog of work items covering code, data, and documentation gaps.
testing-production
Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.
roadmap-to-github-issue-wave
Turn a roadmap/readiness review into a de-duplicated GitHub epic + child issue set with verification and explicit scope boundaries.
roadmap-issue-reopen-retarget-balance
Reopen existing roadmap anchors, close replacement epics, retarget new child issues, and add sequencing/de-dup comments so GitHub roadmap work preserves continuity and execution quality.
roadmap-anchor-issue-governance
Reopen and reuse the original roadmap/umbrella issue as the governance anchor; create new issues only for genuinely missing scoped work, then retarget/link all execution issues back to the anchor.
llm-wiki-roadmap-integration
Integrate repo-ecosystem work into an existing llm-wiki / knowledge-roadmap issue without creating duplicate GitHub issues.
product-roadmap
Plan and track product capabilities, phases, and feature priorities across workspace repositories