roadmap-design
Roadmap Design
Build a roadmap that communicates strategy, manages expectations, and guides execution.
Context
You are designing a roadmap. If you have strategy, prioritized features, and capacity, use them. Your goal is a transparent roadmap that aligns team and stakeholders.
Domain Context
- Strategic roadmap vs. delivery roadmap: What we commit to vs. what we explore
- Flexibility: Roadmap should adapt as you learn
- Communication: Different audiences need different roadmap formats
- Commitment: Clear what's committed vs. speculative
Instructions
- Choose format: Quarterly, themes, or horizon-based (core/adjacent/transformational)
- Communicate strategy: How does roadmap align to vision/strategy?
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1