Agent skill

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.

Stars 133
Forks 19

Install this agent skill to your Project

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

Metadata

Additional technical details for this skill

author
product-on-purpose
category
ideation
frameworks
[
    "triple-diamond",
    "lean-startup",
    "design-thinking"
]

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

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 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.

  3. 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.

  4. 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.

  5. 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.

  6. Identify Risks and Mitigations Surface the biggest risks to success and your plan to address them. This builds stakeholder confidence and surfaces concerns early.

  7. Outline Next Steps Provide 3-5 immediate actions to move the solution forward. Be specific about who does what.

Output Format

Use the template in references/TEMPLATE.md to structure the output.

Quality Checklist

Before finalizing, verify:

  • Brief fits on one page when printed (approximately 500-700 words)
  • Problem recap is concise (2-3 sentences maximum)
  • Solution description avoids technical jargon
  • Features are limited to 3-5 essential capabilities
  • Trade-offs are explicitly stated
  • Next steps are specific and actionable

Examples

See references/EXAMPLE.md for a completed example.

Expand your agent's capabilities with these related and highly-rated skills.

product-on-purpose/pm-skills

init-project

Initialize projects with agentic coding structure. Use when setting up a new project, adding AI agent support to existing project, or when user says "init", "initialize", "setup project", or "scaffold". Creates AGENTS folder, documentation templates, and _NOTES scratch space.

133 19
Explore
product-on-purpose/pm-skills

init-project-jpkb

Initialize new JPKB projects with standardized documentation and folder structure. JPKB-specific version with category folders and fixed base path. Use when creating a new project in the jpkb repository, when the user says "init project", "new project", or when the target is the JPKB projects folder.

133 19
Explore
product-on-purpose/pm-skills

wrap-session

End-of-session documentation workflow that updates README, CHANGELOG, agent context files, and creates session logs. Use when wrapping up a working session, when asked to document session progress, when preparing handoff documentation, or when the user says "wrap up", "end session", "document progress", or "save session".

133 19
Explore
product-on-purpose/pm-skills

skill-template

133 19
Explore
product-on-purpose/pm-skills

utility-update-pm-skills

Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.

133 19
Explore
product-on-purpose/pm-skills

utility-update-pm-skills

Validates internet access, compares the locally installed pm-skills version against the latest public release, and updates local files with conflict-aware overwrite-or-skip options. Produces an update report listing changed files, skipped files, and new capabilities. Use when you want to bring a local pm-skills installation up to date.

133 19
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results