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

> List of initiatives to prioritize. Optional: existing scores, strategic priorities, constraints.

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 read steps in a row, read them all at once (in parallel).

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

## Steps

1. [Read Prioritization Guide]: Read the documentation in: `./skills/sauna/[skill_id]/references/product.prioritization.guide.md` (Get prioritization frameworks and output template)

2. Gather context from the user:

1. **The initiatives** — What are we prioritizing?
   - Get a list with brief descriptions
   - Ask for any existing scores or estimates they have

2. **Prioritization criteria** — What matters?
   - Impact (on users, revenue, strategic goals)
   - Effort/cost (engineering time, complexity)
   - Confidence (how sure are we about estimates)
   - Strategic alignment (fits company direction)
   - Risk (what could go wrong)

3. **Framework preference** — How should we score?
   - RICE (quantitative, good for many initiatives)
   - ICE (simpler, good for quick decisions)
   - Value vs Effort matrix (visual, good for stakeholder alignment)
   - Custom criteria (if they have specific needs)

4. **Constraints** — What limits choices?
   - Resource availability
   - Dependencies between initiatives
   - Timeline requirements
   - Technical debt considerations

Check `./documents/product/profile.yaml` for strategic context.


3. Prepare initiative data for scoring. For each initiative, gather:

**For RICE framework:**
- Reach: users affected per quarter (100, 1000, 10000)
- Impact: 3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal
- Confidence: 1.0=high, 0.8=medium, 0.5=low
- Effort: person-months to complete

**For ICE framework:**
- Impact: 1-10 scale
- Confidence: 1-10 scale
- Ease: 1-10 scale (inverse of effort)

Write the initiative data to `./documents/tmp/initiatives.json` in this format:
{
  "framework": "rice",
  "initiatives": [
    {"name": "Feature A", "reach": 5000, "impact": 2, "confidence": 0.8, "effort": 3},
    ...
  ]
}


4. [Gather Arguments: RICE/ICE Calculator] The next step has the following requirements for arguments, do not proceed until you have all the required information:
- `inputFile`: ./documents/tmp/initiatives.json
- `outputFile`: ./documents/tmp/prioritization-scores.json
- `sensitivity` (default: "false"): true

5. [Run Code: RICE/ICE Calculator]: Call `run_script` with:

```json
{
  "file": {
    "path": https://sk.ills.app/code/product.rice.calculator/preview,
    "args": [
      "inputFile",
      "outputFile",
      "sensitivity"
    ]
  },
  "packages": null
}
```

6. Read `./documents/tmp/prioritization-scores.json` and present the prioritized roadmap:

1. **Ranked list** with scores and formula breakdown
2. **Detailed scoring** for top initiatives with rationale
3. **Sensitivity analysis** showing how rankings change if estimates shift
4. **Strategic alignment check** tied to business goals
5. **Clear recommendations** (P0, P1, reconsider)
6. **Open questions** that could change rankings

Use the output template from the prioritization guide.
Make the ranking actionable—stakeholders should know what to do next.


7. After presenting:

- Ask if any scores feel off based on their domain knowledge
- Offer to adjust estimates and re-run the calculator
- Ask if they want to dive deeper on any initiative
- **Cross-framework prompt:** "Want to design an experiment to validate the top priority before committing resources?"
- Offer to save strategic context to `./documents/product/profile.yaml`