From pm-ai-partner
Guides creation of structured product briefs, PRDs, and feature specs with templates for problems, solutions, metrics, scope, dependencies, and timelines.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin pm-ai-partnerThis skill is limited to using the following tools:
Guide the creation of clear, actionable product briefs that engineering can use to scope and build.
Generates a concise 1-2 page structured PRD from product ideas or feature descriptions, resolving ambiguities and enforcing decisions for engineering teams.
Writes structured, evidence-based PRDs with measurable goals, prioritized requirements, success metrics, and scope boundaries. Use for PRD, product spec, or feature requirements requests.
Generates Product Requirements Documents (PRDs) with user stories, success metrics, scope, technical considerations, and risks for product features.
Share bugs, ideas, or general feedback.
Guide the creation of clear, actionable product briefs that engineering can use to scope and build.
Every product brief should include:
# [Feature Name]
## Problem Statement
What problem are we solving? Who has this problem? Why does it matter now?
## Proposed Solution
What are we building? (High-level, not implementation details)
## User Value
Why will users care? What's the benefit?
## Success Metrics
| Metric | Current | Target |
|--------|---------|--------|
| Primary metric | X | Y |
| Secondary metric | A | B |
## Scope
### In Scope
- What's included in v1
### Out of Scope
- What we're explicitly NOT doing (and why)
## Open Questions
- Things we need to figure out before/during implementation
## Dependencies
- Other teams, systems, or work this depends on
## Timeline
- Target dates (if known), or "TBD pending scoping"
User: Help me write a product brief for adding voice messages to our chat feature.
Good Response:
Let me gather some context first:
Based on what you share, I'll draft the brief. Here's a starting structure:
[To be filled based on your context]
Initial draft based on common patterns: Users in messaging-heavy markets (Brazil, India, SEA) prefer voice over text — it's faster and more personal. Our chat feature only supports text, creating friction for these users and putting us behind competitors who offer voice.
Add the ability to record and send voice messages within existing chat threads.
Core functionality:
| Metric | Current | Target |
|---|---|---|
| Voice messages sent/DAU | 0 | 5% |
| Chat engagement (messages/user) | X | +15% |
| Market-specific DAU (Brazil) | Y | +10% |
What context can you fill in? I'll refine based on your input.
User: I need a brief for adding a "remind me" button to push notifications.
Good Response:
Quick brief mode — I'll draft based on common patterns, you refine:
Users who see a push notification but aren't ready to act have no way to come back to it. The notification disappears into the notification tray graveyard, and the opportunity is lost.
Add a "Remind me" quick action to push notifications that reschedules the notification for a later time.
Options presented to user:
| Metric | Current | Target |
|---|---|---|
| Reminder usage rate | n/a | 5% of notifications |
| Reminded notification action rate | n/a | 40% (vs 12% overall) |
| Notification dismissal rate | 35% | 25% |
Anything to adjust or add?
Structured product brief and PRD creation assistant that guides product managers through writing clear, actionable feature specifications that engineering can scope and build from.
Complete product briefs including problem statement, proposed solution, user value proposition, measurable success metrics with baselines and targets, scoped in/out decisions with rationale, open questions, dependencies, and timeline estimates.
When the user cannot articulate the problem clearly, use jobs-to-be-done framing to help them discover it. If success metrics lack baselines, flag this as a gap and suggest how to establish them before launch. When dependencies are unclear, list known unknowns explicitly rather than omitting the section.