Product Management Plugin

Last verified: 13 February 2026 | Applies to: Pro, Max, Team, Enterprise

In 30 seconds

The Product Management plugin gives Claude fluency in product frameworks — RICE scoring, MoSCoW prioritisation, feature specification writing, and stakeholder communication. It handles the structured documentation that PMs spend hours on, so you can spend more time talking to customers and making decisions.

Key commands

Command	What it does
/feature-spec	Generates a structured feature specification from your description

What it knows

The Product Management plugin’s skills cover:

• Feature specifications — structured PRDs with user stories, acceptance criteria, technical requirements, and success metrics
• Roadmap prioritisation — RICE (Reach, Impact, Confidence, Effort), MoSCoW (Must/Should/Could/Won’t), weighted scoring, and ICE frameworks
• Stakeholder communications — status updates, launch announcements, and cross-functional briefs tailored to different audiences
• User research synthesis — patterns from interview notes, survey data, and support tickets
• Competitive analysis — feature comparison matrices and positioning maps

How operators use it

Feature specs:

/feature-spec — We need to add SSO support to our product. Target users: enterprise IT admins. Should support SAML 2.0 and OIDC. Must integrate with our existing auth system. Timeline: Q2.

Claude produces a structured spec with user stories, acceptance criteria, technical requirements, edge cases, and success metrics.

Prioritisation:

Here are 15 feature requests from the last quarter [list or upload]. Score them using RICE framework. Our primary goal this quarter is reducing churn.

Claude applies RICE scoring, adjusting for the stated goal, and produces a prioritised ranked list with rationale.

Stakeholder updates:

Write three versions of our Q1 product update: (1) for the board — focus on revenue impact and strategic direction, (2) for engineering — technical details and upcoming sprint priorities, (3) for customers — new features and how to use them.

Research synthesis:

Here are notes from 12 customer interviews [upload]. Identify the top 5 recurring themes, classify each by urgency, and suggest which ones represent opportunities vs. churn risks.

The honest take

What works well

• Feature spec generation is strong — the output is structured, thorough, and follows PM best practices.
• RICE/MoSCoW scoring is well-executed and saves time on prioritisation exercises.
• Stakeholder comms for different audiences is genuinely useful — adapting the same information for board vs. engineering vs. customers.

What doesn’t work as well

• Prioritisation frameworks are only as good as your input. If you don’t provide realistic effort estimates or reach data, the scores will be misleading.
• Claude can’t replace the qualitative judgement that comes from direct customer interaction.
• Research synthesis works best with structured notes. Messy, freeform interview notes produce less reliable patterns.

Who it’s best for: Product managers, product leads, and founders wearing the PM hat. Anyone who spends too much time on documentation and not enough on discovery and decision-making.

Related

• All Plugins
• Plugin Commands Reference

---

Something wrong or outdated? Let us know →

Get weekly workflows — subscribe to the newsletter.