name: product-prioritization-manager
description: Run RICE, MoSCoW, Impact/Effort, and weighted scoring sessions on your backlog, including Asana-backed backlogs.

Product Prioritization Manager Skill

A backlog scoring skill that helps you choose what to ship next using RICE, MoSCoW, Impact/Effort matrices, and custom weighted scoring.

When to use this skill

Use this skill when you say:
- “Score this backlog with RICE.”
- “Help me categorize these features with MoSCoW.”
- “Make an impact vs effort matrix for these ideas.”
- “Pull my Asana backlog and prioritize it.”

Inputs this skill uses

Backlog items can come from:
- Asana (via MCP): project, portfolio, or search term.
- CSV pasted into chat.
- Manual list of items (feature name + short description).

Optionally provide:
- Constraints (timeframe, team capacity, product area).
- Existing fields (custom fields in Asana like reach, impact, effort, etc.).

Core behaviors

A. RICE scoring (RI)

• For each item, capture or estimate:
• Reach (e.g., users/quarter).
• Impact (0.25, 0.5, 1, 2, 3).
• Confidence (%).
• Effort (person-months or sprints).
• Use Asana custom fields where they map naturally.
• Compute RICE score = (Reach × Impact × Confidence) / Effort.
• Output:
• Ranked table: Rank | Item | Reach | Impact | Confidence | Effort | RICE Score.
• Short summary and top 3 recommendations.
• Flag items with low confidence (< 50%) for further validation.

B. MoSCoW prioritization (MO)

• Walk through each item and assign:
• Must Have, Should Have, Could Have, or Won’t Have (this time).
• Check capacity sanity:
• Must Haves should not exceed ~60% of capacity.
• Output:
• Four grouped lists with one-line rationale per item.
• Call out if Must Haves are overloaded and suggest candidates to downgrade.

C. Impact vs Effort matrix (IE)

• Score each item:
• Impact 1–5.
• Effort 1–5.
• Map to quadrants:
• Quick Wins, Big Bets, Fill-ins, Money Pits.
• Output:
• Table: Item | Impact | Effort | Quadrant.
• Count per quadrant and recommendation (“Start with these Quick Wins…”).

D. Custom weighted feature scoring (WS)

• Define or confirm scoring dimensions and weights (summing to 100%).
• Score each item 1–10 per dimension.
• Compute weighted score and rank.
• Output:
• Table: Rank | Feature | dimension scores | Weighted Score.
• Highlight top 3, with short rationale.

E. Asana-backed backlog session (BP)

• Ask which Asana project / portfolio / search term to use.
• Fetch items via Asana tools (tasks, custom fields, status).
• Let you pick a framework (RICE, MoSCoW, IE, or WS) and run it end-to-end.
• Offer to:
• Update Asana custom fields with scores.
• Produce a summary document you can save or share.

Output format

• Always include:
• Short narrative summary (what framework, how many items).
• Clear, ranked or grouped tables.
• Optional export suggestion (CSV / Markdown or Asana field updates).*** End Patch