develop-solution-brief
Develop Solution Brief generates a focused one-page document that frames your proposed solution, highlights essential features, and surfaces trade-offs for stakeholder alignment. Use it to pitch approach, bridge problem understanding to specification, or compare solution options without implementation details.
Develop Solution Brief creates a one-page overview to pitch your solution approach and align stakeholders on key decisions.
AI-generated summary based on this skill's SKILL.md
Install
product-on-purpose/pm-skills/develop-solution-brief · repository language: JavaScript
git clone https://github.com/product-on-purpose/pm-skills
cp -r pm-skills/skills/develop-solution-brief ~/.claude/skills/develop-solution-briefnpx skillfed install product-on-purpose/pm-skills/develop-solution-briefFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I write a solution brief?
Develop Solution Brief guides you through creating a focused one-page document that frames your proposed solution, highlights essential features, and surfaces trade-offs for stakeholder alignment. Start by stating the problem, outline your approach, list key features, identify trade-offs, and define success metrics—all concisely enough to fit one page. This structure lets you pitch to leadership, align cross-functional teams, and document intent before detailed specification work begins.
What is a solution brief vs. a PRD?
Develop Solution Brief produces a high-level, one-page overview that frames approach and trade-offs without implementation detail. A PRD (Product Requirements Document) is a detailed specification covering requirements, acceptance criteria, and technical scope. Use the solution brief early to align stakeholders on direction and compare options; use a PRD later to guide engineering and QA through execution.
What should a solution brief template include?
Develop Solution Brief templates typically include: problem statement, proposed solution approach, key features, trade-offs analysis, risks and mitigations, success metrics, and stakeholder alignment notes. The one-page format forces prioritization—include only what matters most to decision-making and team alignment, leaving detailed specs for later documents.
How does Develop Solution Brief help align teams?
Develop Solution Brief creates a shared reference document that cross-functional teams use to understand what will be built and why. By surfacing trade-offs, risks, and success metrics upfront, it reduces misalignment during execution. Teams can reference the brief to resolve scope questions and stay focused on the chosen approach rather than revisiting fundamental decisions.
Can I use a solution brief to compare multiple options?
Yes. Develop Solution Brief supports comparing solution options at a high level with trade-offs. Create a brief for each option, highlighting approach differences, feature trade-offs, and risk profiles. This lets stakeholders and teams evaluate alternatives before committing to detailed specification, making the decision process faster and more transparent.
What are solution brief key features and success metrics?
Develop Solution Brief helps you list the essential features that differentiate your approach and define how you'll measure success. Key features are the core capabilities that solve the problem; success metrics are quantifiable outcomes (adoption, performance, cost reduction) that validate the solution worked. Both belong in the brief to clarify intent and enable post-launch evaluation.
SKILL.md
rendered from the published skill — quoted content, verbatim
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 5 files
skills/develop-solution-brief/HISTORY.md
skills/develop-solution-brief/SKILL.md
skills/develop-solution-brief/evals/trigger-fixtures.json
skills/develop-solution-brief/references/EXAMPLE.md
skills/develop-solution-brief/references/TEMPLATE.md