To run this task you must have the following required information:

> Product goals, known initiatives or problems to solve, and preferred timeframe format

If you don't have all of this information, exit here and respond asking for any extra information you require, and instructions to run this task again with ALL required information.

---

You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple CONSECUTIVE read steps in a row, read them all at once (in parallel). Otherwise, do not read a file until you reach that step.

Add all steps to your todo list now and begin executing.

## Steps

1. [Read Roadmap Guide]: Read the documentation in: `skills/sauna/[skill_id]/references/product.roadmap.guide.md`

2. [Read Projects]: Discover relevant information in the user's filesystem at `documents/work/projects/**/*.md`. (Check for existing strategy, priorities, and user segments)

3. Review any existing strategy and priorities from the loaded product context.

Gather roadmap inputs:

STRATEGIC CONTEXT
- Product vision (where are you going?)
- Key goals for this period (6-12 months)
- Target users/segments

INITIATIVES
- What problems need solving?
- What opportunities exist?
- What's been requested by customers/stakeholders?

CONSTRAINTS
- Team size and capacity
- Known dependencies or blockers
- Committed deliverables

FORMAT PREFERENCE
- Now/Next/Later (flexibility)
- Quarterly view (planning alignment)
- Theme-based (strategy focus)


4. Structure the roadmap:

THEMES
- Group initiatives into 3-5 strategic themes
- Each theme should connect to a business goal
- Name themes by outcome, not feature area

INITIATIVES PER THEME
For each initiative include:
- Problem statement (1-2 sentences)
- Success metric
- Rough sizing (S/M/L)
- Confidence level (High/Medium/Low)

TIMEFRAME PLACEMENT
- Now: High confidence, ready to start, high priority
- Next: Important, some discovery needed
- Later: On radar but not urgent

Present as a clear visual structure (table or organized list).


5. Add roadmap context:
- Brief strategic rationale at top (3-4 sentences)
- "Not doing" section with 2-3 items explicitly deprioritized
- Key dependencies or risks to flag


6. Save the roadmap to `documents/work/projects/**/*.md` as roadmap.md:
- Strategic themes and initiatives
- Now/Next/Later placement
- Key metrics and success criteria
- Date created

This becomes the reference for future product discussions and prioritization.