roadmap-planning

name	roadmap-planning
effort	high
description	Use when product goals or competing initiatives need to become a sequenced, stakeholder-ready roadmap. Triggers on: "로드맵 만들어줘", "분기 계획", "roadmap planning", "이니셔티브 우선순위 정해줘", feature list를 outcome 기반으로 바꿔줘", "Q2 로드맵", "분기별 계획 세워줘", "이해관계자 정렬".
scenarios	["경쟁 이니셔티브 15개가 있는데 Q2 로드맵 만들어줘","6개월 제품 로드맵을 세 팀 걸쳐 계획해야 해","Help me build a roadmap that execs will actually approve","feature list를 outcome 중심 로드맵으로 바꿔줘","분기 계획 수립 어떻게 해야 해?","We need to sequence work across multiple teams"]
type	workflow
theme	strategy-positioning
estimated_time	1-2 weeks (active facilitation: 45-90 min/day)
compatibility	{"recommended":["sequential-thinking"],"optional":["think-tool"],"remote_mcp_note":"sequential-thinking이 있으면 에픽 의존성 그래프를 체계적으로 열거하고 위상 정렬할 수 있습니다. Claude 설정 → MCP Servers에서 remote SSE 엔드포인트를 추가하세요."}

Standing Mandates

• ALWAYS map dependencies between epics before sequencing — unresolved dependencies invalidate the order.
• ALWAYS distinguish committed items from aspirational items explicitly.
• NEVER build a roadmap without real capacity constraints from the team.
• NEVER sequence work without stakeholder alignment on the top-level outcome priorities.

Key Concepts

What is Strategic Roadmap Planning?

Roadmap planning is the process of:

1. Gathering inputs — Customer problems, business goals, technical constraints
2. Defining initiatives — Epics with clear hypotheses and success metrics
3. Prioritizing — Rank initiatives by impact, effort, strategic fit
4. Sequencing — Organize into releases/quarters with logical dependencies
5. Communicating — Present roadmap to stakeholders with strategic narrative

For roadmap type descriptions (Now/Next/Later, Theme-Based, Timeline, Feature-List anti-pattern) and the rationale for this approach, see references/roadmap-types.md.

Anti-Patterns (What This Is NOT)

• Not a commitment: Roadmaps are strategic plans, not contracts
• Not a feature list: Roadmaps frame problems, not just solutions
• Not waterfall: Roadmaps evolve quarterly based on learning

When to Use This

• Annual or quarterly planning cycles
• After product strategy session (translate strategy to roadmap)
• Onboarding new stakeholders (align on direction)
• Reframing existing roadmap (shift from feature-driven to outcome-driven)

When NOT to Use This

• For tactical sprint planning (use backlog instead)
• When strategy is unclear (run product-strategy-session first)
• When stakeholders expect date commitments (address expectations first)

---

Facilitation Source of Truth

When running this workflow as a guided conversation, use workshop-facilitation as the interaction protocol and delegate to agents/roadmap-coordinator.md for entry mode selection, Phase 1 intake question sequence, sub-skill handoff triggers, and loop-back conditions.