develop-solution-brief

Generate a one-page solution brief with problem recap, approach, metrics, and next steps.

527|69|Updated Jan 9, 2026

Search Tags:#trade-offs #stakeholder-alignment #decision-records #solution-brief #problem-recap

Ready to run

npx skills add https://github.com/product-on-purpose/pm-skills --skill develop-solution-brief

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: develop-solution-brief
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-solution-brief
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill develop-solution-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams communicate solution intent concisely, bridging problem understanding and detailed specifications for stakeholder alignment.

Core Features & Use Cases

One-page Solution Brief Template: A ready-to-fill structure covering problem recap, proposed solution, key features, metrics, trade-offs, risks, and next steps.
Structured Decision Records: Clear documentation of decisions and rationale to accelerate reviews and approvals.
Use Case Scenarios: Examples demonstrating how teams apply the brief during ideation, planning, and governance.

Quick Start

Generate a concise solution brief for a new feature proposal, including problem recap, proposed approach, success metrics, and next steps. Provide a 1-page summary suitable for stakeholders.

Frequently Asked Questions about develop-solution-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write a solution brief for stakeholder alignment?▼

To write a solution brief for stakeholder alignment, use a templated structure covering problem recap, proposed approach, key decisions, trade-offs, and next steps. This ensures concise communication of solution intent before detailed specifications.

What is the best way to document trade-offs and decisions for a proposed solution?▼

Documenting trade-offs and decisions for a proposed solution requires structured decision records. This approach captures the rationale behind key choices, accelerating stakeholder reviews and approvals while maintaining a clear history of solution intent.

How do I pitch a proposed solution approach to cross-functional teams?▼

To pitch a proposed solution approach to cross-functional teams, generate a concise one-page summary. This brief format highlights the problem recap, proposed solution, success metrics, and next steps to ensure fast alignment and governance.

Do I need a solution brief before creating detailed specs?▼

A solution brief is needed before creating detailed specs to bridge problem understanding and execution. It provides a ready-to-fill structure for proposed features, ensuring stakeholders align on key decisions and trade-offs prior to detailed planning.

What limitations exist when using a one-page solution brief template?▼

A one-page solution brief template is limited to high-level solution intent, problem recap, and key metrics. It is not designed for detailed specifications, meaning teams must transition to deeper documentation after initial stakeholder alignment is achieved.