From pm-skills
Creates a one-page solution overview to pitch proposed approach, key decisions, and trade-offs to stakeholders. Use when aligning teams or documenting solution intent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:develop-solution-briefThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
A solution brief is a concise, one-page document that communicates the proposed solution to a problem. It serves as the bridge between problem understanding and detailed specification, providing enough context for stakeholders to align on the approach without getting lost in implementation details. The one-page constraint forces clarity and prioritization.
deliver-prd; the brief pitches, the PRD specifiesdefine-problem-statement firstdevelop-adr (technical) or develop-design-rationale (design)foundation-lean-canvasWhen asked to create a solution brief, follow these steps:
Recap the Problem Summarize the problem in 2-3 sentences maximum. Don't re-explain the full problem statement - reference it if needed. The reader should immediately understand what pain point this solution addresses.
Describe the Proposed Solution Explain what you're building in clear, non-technical language. Focus on the user experience and core value proposition. Avoid implementation details - this is about what, not how.
List Key Features Identify 3-5 essential features that comprise the solution. These should be the minimum set needed to solve the problem. Resist the urge to include nice-to-haves - the one-page constraint demands focus.
Define Success Metrics Connect the solution to measurable outcomes. How will you know if this works? Reference metrics from the problem statement and set targets.
Acknowledge Trade-offs Document what you're explicitly NOT doing and why. Good solution briefs are honest about scope limitations and alternatives that were considered but rejected.
Identify Risks and Mitigations Surface the biggest risks to success and your plan to address them. This builds stakeholder confidence and surfaces concerns early.
Outline Next Steps Provide 3-5 immediate actions to move the solution forward. Be specific about who does what.
Use the template in references/TEMPLATE.md to structure the output. A complete brief fills every template section: Problem Recap; Proposed Solution; Key Features; Success Metrics; Trade-offs Considered; Risks & Mitigations; and Next Steps.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.
npx claudepluginhub product-on-purpose/pm-skills --plugin pm-skillsCreates concise, decision-ready product specifications (one-pagers and PRDs) to align stakeholders on problem, solution, users, success metrics, and constraints.
Structures product decisions into concise docs with options, trade-offs, comparisons, recommendation, reversibility, and next steps for stakeholder review.
Guides creation of structured product briefs, PRDs, and feature specs with templates for problems, solutions, metrics, scope, dependencies, and timelines.