Develop Solution Brief
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.
Install
/plugin marketplace add product-on-purpose/pm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add product-on-purpose/pm-skills --skill develop-solution-briefgit clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/develop-solution-brief ~/.claude/skills/develop-solution-briefPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Solution Brief 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. ## When to Use - Pitching a solution approach to stakeholders for buy-in - Aligning cross-functional teams on what you're building and why - Documenting solution intent before detailed PRD writing - Comparing multiple solution options at a high level - Communicating product direction to leadership ## When NOT to Use - Stakeholders are aligned and engineering needs the full specification -> use `deliver-prd`; the brief pitches, the PRD specifies - The problem is not yet framed or agreed -> use `define-problem-statement` first - You are recording a decision already made -> use `develop-adr` (technical) or `develop-design-rationale` (design) - You need to compare strategic options across the whole business model -> use `foundation-lean-canvas` ## Instructions When asked to create a solution brief, follow these steps: 1. **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. 2. **Describe the Proposed Solution**
Details
- Skill name
develop-solution-brief- Repository
- product-on-purpose/pm-skills
- Path
skills/develop-solution-brief/SKILL.md- License
- Apache-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Develop Solution Brief skill do?
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.
How do I install the Develop Solution Brief skill?
Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Develop Solution Brief popular?
It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.
Related skills
<phase or Classification Skill Name>
819product-on-purpose/pm-skills
<single-line 20-100 word description; include trigger keywords and do not use folded YAML>
Define Hypothesis
819product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
Define Jtbd Canvas
819product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
Develop Spike Summary
819product-on-purpose/pm-skills
Documents the results of a completed technical or design spike, capturing the original question, approach, evidence-backed findings, and a clear proceed-or-not recommendation so the team does not re-litigate the exploration. Use once a time-boxed investigation has concluded. For the architecture decision the spike informs, use develop-adr instead; for research-based exploration, use discover-interview-synthesis.
Develop Design Rationale
819product-on-purpose/pm-skills
Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.
Discover Market Sizing
819product-on-purpose/pm-skills
Estimate market opportunity (TAM, SAM, SOM) using multiple sizing frameworks (top-down, bottom-up, comparable company, analogous market). Triangulates across frameworks, highlights where they converge and diverge as signal, and produces a calibrated range with source-graded confidence labels. Refuses unbounded fabrications; always offers a labeled lower-confidence path when data is thin. Used for investment cases, go/no-go decisions, and stakeholder pitches.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.