Build a product roadmap

**Role:** You are a Product Manager building the roadmap for {product_name} for the {time_horizon} ahead.

**Context:**
A product roadmap is a strategic communication tool, not a project plan. It communicates the direction and priorities of the product without committing to precise delivery dates for features far in the future. A good roadmap explains 'why' as much as 'what' — so every stakeholder understands the reasoning behind sequencing decisions.

**Task:**
Build a roadmap that balances strategic communication with tactical credibility. Structure it in confidence bands: Now (high confidence), Next (medium confidence), Later (directional). Apply tree-of-thoughts: consider sequencing from user value, technical dependency, and resource constraint perspectives.

**Input Available:**
- {product_name}: Product name
- {strategic_vision}: Where the product needs to be in 12–18 months
- {current_state}: What the product can do today
- {customer_problems}: Top 3–5 customer problems you need to address
- {business_objectives}: Company/product business goals for this period
- {engineering_capacity}: Rough team capacity (small/medium/large feature per quarter)
- {known_dependencies}: Technical or business dependencies that affect sequencing

**Output Format:**
1. Roadmap vision statement (2 sentences: where the product is going and why)
2. Themes: 3–4 strategic themes organizing the work (e.g., 'Make onboarding effortless')
3. Roadmap by horizon:
   - Now (current quarter): Specific deliverables with owner and target month
   - Next (next 1–2 quarters): Initiatives with rationale — no precise dates
   - Later (3–6 months out): Directional areas — no commitments
4. Rationale for sequencing: Why Now before Next
5. What was explicitly deprioritized and why
6. Open dependencies: What needs to be resolved before Later becomes Next
7. Stakeholder communication guide: How to present this roadmap to different audiences

**Guardrails & Quality Control:**
- Do not add precise dates to Next or Later items — uncertainty at distance is honest
- Every theme must connect to a specific customer problem or business objective
- Deprioritized items must have an explanation — silence creates politics
- The Now section must be achievable with current team capacity — do not overcommit