Product Management Plugin

​

Installation

claude plugins add knowledge-work-plugins/product-management

​

What It Does

• Feature Specs & PRDs — Generate structured product requirements documents from a problem statement or feature idea. Includes user stories, requirements prioritization, success metrics, and scope management.
• Roadmap Planning — Create, update, and reprioritize your product roadmap. Supports Now/Next/Later, quarterly themes, and OKR-aligned formats with dependency mapping.
• Stakeholder Updates — Generate status updates tailored to your audience (executives, engineering, customers). Pulls context from connected tools to save you the weekly update grind.
• User Research Synthesis — Turn interview notes, survey data, and support tickets into structured insights. Identifies themes, builds personas, and surfaces opportunity areas with supporting evidence.
• Competitive Analysis — Research competitors and generate briefs with feature comparisons, positioning analysis, and strategic implications.
• Metrics Review — Analyze product metrics, identify trends, compare against targets, and surface actionable insights.

​

Commands

​

/write-spec

/write-spec <feature or problem statement>

• /write-spec SSO support
• /write-spec Enterprise customers keep asking for centralized auth
• /write-spec Users want to export their data as CSV

• User problem: What problem does this solve? Who experiences it?
• Target users: Which user segment(s)?
• Success metrics: How will we know this worked?
• Constraints: Technical constraints, timeline, dependencies
• Prior art: Has this been attempted before?

## Problem Statement
The user problem, who is affected, and impact (2-3 sentences)

## Goals
3-5 specific, measurable outcomes tied to user or business metrics

## Non-Goals
3-5 things explicitly out of scope with rationale

## User Stories
As a [user type], I want [capability] so that [benefit]
(grouped by persona)

## Requirements
- Must-Have (P0): Critical requirements with acceptance criteria
- Nice-to-Have (P1): Important but not blocking
- Future Considerations (P2): Out of scope for now

## Success Metrics
- Leading indicators (change quickly)
- Lagging indicators (change over time)
- Specific targets for each

## Open Questions
Unresolved questions tagged with who needs to answer
(engineering, design, legal, data)

## Timeline Considerations
Hard deadlines, dependencies, and phasing

• Project tracker: Pulls related tickets, epics, existing requirements, identifies dependencies
• Knowledge base: Searches research docs, prior specs, meeting notes
• Design tools: Pulls mockups and wireframes

​

/roadmap-update

/roadmap-update

• Now/Next/Later
• Quarterly themes
• OKR-aligned roadmaps
• Dependency mapping

​

/stakeholder-update

/stakeholder-update

• Weekly update
• Monthly update
• Launch announcement
• Ad-hoc update

• Executives: High-level progress, decisions needed, risks
• Engineering: Technical details, blockers, sprint progress
• Customers: Feature announcements, benefits, migration guides

You: /stakeholder-update
Claude: What type of update? (weekly, monthly, launch, ad-hoc)
You: Weekly update for the exec team
Claude: [Pulls context from project management tool, chat, and docs]
Claude: [Generates executive summary with progress, decisions, risks, and next milestones]

​

/sprint-planning

/sprint-planning [sprint name or date range]

1. Define sprint goals and success criteria
2. Estimate team capacity (accounting for PTO, meetings)
3. Scope and prioritize backlog items
4. Identify dependencies and risks
5. Generate sprint plan document

• Project tracker: Pulls backlog, estimates, team velocity, dependencies
• Calendar: Accounts for PTO, holidays, meetings
• Chat: Surfaces blockers and context from team discussions

​

/synthesize-research

/synthesize-research

• Interview transcripts
• Survey data
• Support tickets
• User feedback from multiple sources

• Thematic analysis across all inputs
• Key findings with supporting evidence
• Persona development or refinement
• Opportunity areas prioritized by frequency and impact
• Actionable recommendations

You: /synthesize-research
Claude: What research do you want to synthesize?
You: [Pastes 8 interview transcripts]
Claude: [Identifies themes, patterns, and insights]
Claude: [Generates synthesis with findings, personas, opportunities, and evidence]

​

/competitive-brief

/competitive-brief

You: /competitive-brief
Claude: Which competitor(s) or feature area?
You: Compare our onboarding flow to [competitor A] and [competitor B]
Claude: [Researches competitor onboarding approaches]
Claude: [Generates brief with feature comparison, strengths/weaknesses, strategic implications]

• Feature comparison matrix
• Positioning analysis
• Win/loss insights (from connected CRM)
• Strategic recommendations

​

/metrics-review

/metrics-review

• Metric trend analysis
• Comparison against targets
• Anomaly detection
• Actionable optimization recommendations
• Dashboard design suggestions

​

Skills

​

Prioritization Frameworks

• Reach: How many users affected?
• Impact: How much value for each user?
• Confidence: How certain are we?
• Effort: How much work required?

• Categorizes requirements by necessity
• Useful for scope management and release planning

​

MCP Integrations

​

Example Workflows

​

Writing a PRD

You: /write-spec
Claude: What feature or problem are you speccing out?
You: We need to add SSO support for enterprise customers
Claude: [Asks about target users, constraints, success metrics]
Claude: [Generates full PRD with problem statement, user stories,
         requirements, success metrics, open questions]

​

Preparing a Stakeholder Update

You: /stakeholder-update
Claude: What type of update? (weekly, monthly, launch, ad-hoc)
You: Weekly update for the exec team
Claude: [Pulls context from project management tool, chat, and docs]
Claude: [Generates executive summary with progress, decisions,
         risks, and next milestones]

​

Synthesizing User Research

You: /synthesize-research
Claude: What research do you want to synthesize? You can paste interview
        notes, upload files, or I can pull from connected sources.
You: [Pastes 8 interview transcripts]
Claude: [Identifies themes, patterns, and insights across interviews]
Claude: [Generates synthesis with key findings, personas, opportunity
         areas, and evidence]

​

Competitive Analysis

You: /competitive-brief
Claude: Which competitor(s) or feature area do you want to analyze?
You: Compare our onboarding flow to [competitor A] and [competitor B]
Claude: [Researches competitor onboarding approaches]
Claude: [Generates brief with feature comparison, strengths/weaknesses,
         and strategic implications]

​

Best Practices

​

For Specs

• Be opinionated about scope — tight specs are better than expansive vague ones
• If an idea is too big, break it into phases and spec the first phase
• Success metrics should be specific and measurable, not vague
• Non-goals are as important as goals (they prevent scope creep)

​

For Research Synthesis

• More context = better insights — provide as much raw research as possible
• Claude looks for patterns across multiple sources
• Tag any known constraints or business context upfront

​

For Stakeholder Updates

• Tailor by audience — execs want decisions and risks, engineers want technical details
• Pull context from connected tools to save time
• Be transparent about blockers and dependencies