develop-solution-brief

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Solution Brief
3 
4A 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.
5 
6## When to Use
7 
8- Pitching a solution approach to stakeholders for buy-in
9- Aligning cross-functional teams on what you're building and why
10- Documenting solution intent before detailed PRD writing
11- Comparing multiple solution options at a high level
12- Communicating product direction to leadership
13 
14## When NOT to Use
15 
16- Stakeholders are aligned and engineering needs the full specification -> use `deliver-prd`; the brief pitches, the PRD specifies
17- The problem is not yet framed or agreed -> use `define-problem-statement` first
18- You are recording a decision already made -> use `develop-adr` (technical) or `develop-design-rationale` (design)
19- You need to compare strategic options across the whole business model -> use `foundation-lean-canvas`
20 
21## Instructions
22 
23When asked to create a solution brief, follow these steps:
24 
251. **Recap the Problem**
26…