User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs.
Install Develop Solution Brief
$ npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills develop-solution-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/develop-solution-brief .claude/skills/develop-solution-brief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "develop-solution-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-solution-brief into .claude/skills/develop-solution-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-solution-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-solution-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills develop-solution-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/develop-solution-brief .agents/skills/develop-solution-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "develop-solution-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-solution-brief into .agents/skills/develop-solution-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-solution-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills develop-solution-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/develop-solution-brief .cursor/skills/develop-solution-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "develop-solution-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-solution-brief into .cursor/skills/develop-solution-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-solution-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/product-on-purpose/pm-skills.git --path skills/develop-solution-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills develop-solution-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/develop-solution-brief .gemini/skills/develop-solution-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "develop-solution-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-solution-brief into .gemini/skills/develop-solution-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-solution-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install product-on-purpose/pm-skills develop-solution-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/develop-solution-brief .github/skills/develop-solution-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "develop-solution-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-solution-brief into .github/skills/develop-solution-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-solution-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills develop-solution-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/develop-solution-brief .opencode/skills/develop-solution-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "develop-solution-brief" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-solution-brief into .opencode/skills/develop-solution-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-solution-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
develop-solution-brief- GitHub stars
- 715
- Token cost
- ~961 tokens
- SKILL.md length
- 438 words
- Files
- 5 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs.
- Works in 7 steps: Recap the Problem → Describe the Proposed Solution → List Key Features → …
- Pitching solutions to stakeholders
- SKILL.md covers When to Use, When NOT to Use, Instructions and Output Format, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Develop Solution Brief is an agent skill from product-on-purpose/pm-skills. 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.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `HISTORY.md`, `evals/trigger-fixtures.json` and `references/EXAMPLE.md`).
It sits in Product & Project Management. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
When your agent uses it
- Pitching solutions to stakeholders
- Aligning teams on approach
- Documenting solution intent before detailed specification
Example prompts
- “Use the develop-solution-brief skill to create a concise one-page solution overview that communicates the proposed approach, key decisions, and…”
- “/develop-solution-brief”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Recap the Problem
- Describe the Proposed Solution
- List Key Features
- Define Success Metrics
- Acknowledge Trade-offs
- Identify Risks and Mitigations
- Outline Next Steps
What it can do on your machine
Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Develop Solution Brief loads about 961 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 438 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 438 words, ~961 tokens.
Download SKILL.mdSave it as
.claude/skills/develop-solution-brief/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- develop-solution-brief
- description
- 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.
- license
- Apache-2.0
- metadata.phase
- develop
- metadata.version
- 2.1.0
- metadata.updated
- 2026-06-10
- metadata.category
- ideation
- metadata.frameworks
- triple-diamond, lean-startup, design-thinking
- metadata.author
- product-on-purpose
<!-- 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 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-statementfirst - You are recording a decision already made -> use
develop-adr(technical) ordevelop-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:
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.
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.
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.
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.
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.
Identify Risks and Mitigations Surface the biggest risks to success and your plan to address them. This builds stakeholder confidence and surfaces concerns early.
Outline Next Steps Provide 3-5 immediate actions to move the solution forward. Be specific about who does what.
Show full SKILL.md (84 more words)Show less
Output Format
Use the template in references/TEMPLATE.md to structure the output. A complete brief fills every template section: Problem Recap; Proposed Solution; Key Features; Success Metrics; Trade-offs Considered; Risks & Mitigations; and Next Steps.
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.
© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/develop-solution-brief of product-on-purpose/pm-skills.
- SKILL.md
- HISTORY.md
- evals/trigger-fixtures.json
- references/EXAMPLE.md
- references/TEMPLATE.md
Open the folder on GitHubat commit 1cef1a9
Compare with similar skills
Develop Solution Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Develop Solution Brief this skillproduct-on-purpose/pm-skills | 715 | — | ~961 | Automated safety check: Pass | Apache-2.0 | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convex Create Componentspokvulcan/poker-planning | 114 | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Self Improving Agentfarm-fe/farm | 5.6k | 2 repos | ~3.3k | Automated safety check: Notes | MIT |
Similar skills
Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Convex Create Component
spokvulcan/poker-planning
Builds reusable Convex components with isolated tables and app-facing APIs.
Self Improving Agent
farm-fe/farm
A universal self-improving agent that learns from ALL skill experiences.
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Define Jtbd Canvas
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
Deliver Acceptance Criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.
Deliver Launch Checklist
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Related
Categories
Questions about Develop Solution Brief
What does Develop Solution Brief do?
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Develop Solution Brief is an agent skill from product-on-purpose/pm-skills. Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs.
When should I use Develop Solution Brief?
Develop Solution Brief fits situations like: pitching solutions to stakeholders; aligning teams on approach; documenting solution intent before detailed specification.
How do I install Develop Solution Brief in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a claude-code`. Or copy the skill folder (skills/develop-solution-brief in product-on-purpose/pm-skills) into .claude/skills/develop-solution-brief in your project. Claude Code loads it when a task matches its description.
How do I install Develop Solution Brief in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a codex`. Or copy the skill folder (skills/develop-solution-brief in product-on-purpose/pm-skills) into .agents/skills/develop-solution-brief in your project. Codex loads it when a task matches its description.
Can I use Develop Solution Brief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill develop-solution-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/develop-solution-brief, .gemini/skills/develop-solution-brief, .github/skills/develop-solution-brief and .opencode/skills/develop-solution-brief in your project.
What does Develop Solution Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Develop Solution Brief is instructions for the agent only.
Does Develop Solution Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Develop Solution Brief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Develop Solution Brief use?
Develop Solution Brief is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Develop Solution Brief use?
About 961 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Develop Solution Brief?
Skills that share tags, products or a category with Develop Solution Brief: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Develop Solution Brief?
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 715 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 4, 2026.
Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.