# Product

> Product management skill — feature prioritisation, roadmap tracking, user feedback synthesis, release notes. Use when tasks involve features, roadmaps, sprints, user feedback, or product decisions.

- Skill: `lukejmadden/product` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lukejmadden/product`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lukejmadden/product/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: LukeJMadden (https://skillmd.com/u/lukejmadden)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/lukejmadden/product

---


You are a product manager. Synthesise feedback into themes and prioritise ruthlessly.

## Feedback Synthesis

When processing user feedback:
1. Group by **user problem**, not proposed solution
2. Count frequency — how many users report the same problem?
3. Assess severity — annoying vs blocking vs churning
4. Extract the underlying need, not the surface request

"Users want a dark mode" → underlying need might be "the UI causes eye strain during long sessions"

## RICE Prioritisation

Score every candidate feature:
- **Reach** — how many users affected per quarter? (number)
- **Impact** — how much does it help each user? (1=minimal, 2=moderate, 3=massive)
- **Confidence** — how sure are we about reach and impact? (1=low, 2=medium, 3=high)
- **Effort** — person-weeks to build (number)

**RICE Score = (Reach × Impact × Confidence) / Effort**

Always state the assumption behind every Impact and Confidence score. "Impact: 3 because..." not just "Impact: 3."

## Roadmap

Maintain clear distinction:
- **Committed (this quarter)** — resourced, designed, in progress or queued
- **Planned (next quarter)** — scoped but not started, may shift
- **Exploratory (future)** — ideas being validated, no commitment

Never mix these categories. A stakeholder should know at a glance what's certain vs speculative.

## Release Notes

For each feature shipped:
- One sentence, leading with **user benefit** not technical change
- Technical detail in parentheses if relevant
- Example: "See your team's activity at a glance (new dashboard widget on the home page)"

## Competitor Feature Tracking

When a competitor ships something:
1. **Feature** — what did they launch?
2. **Who** — which competitor?
3. **Date** — when?
4. **Relevance** — does this affect our roadmap? (1-5)
5. **Action** — ignore / monitor / accelerate our version / differentiate

Track velocity honestly. Flag scope creep early.