develop-solution-brief SKILL.md skillA
develop-solution-brief from product-on-purpose/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add product-on-purpose/pm-skills/develop-solution-brief@v2.1.0Pins v2.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- product-on-purpose/pm-skills
- Path
skills/develop-solution-brief/SKILL.md- Versions recorded
- 5
- Latest version
- v2.1.0, committed Jun 10, 2026
- First version recorded
- Mar 25, 2026
- Size
- 3,842 bytes
- Repository stars
- 790
- License
- Apache-2.0
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- 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-statement` first - You are recording a decision already made -> use `develop-adr` (technical) or `develop-design-rationale` (design) …
Read the whole file at its exact version.
How to install
mdr add product-on-purpose/pm-skills/develop-solution-brief@sha256:0cb3407abb6f61a8The line at the top of this page pins the label v2.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_usw5sno24vnlooxc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 25, 2026 and Jun 10, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.0 latest | 2026-06-10 | 152b175 | 3,842 B | A | view · diff |
| v2.0.0 | 2026-06-10 | b8ccff6 | 3,216 B | A | view · diff |
| v2.0.0 | 2026-05-20 | be1352b | 3,216 B | A | view · diff |
| v2.0.0 | 2026-04-23 | 8ab0f81 | 3,210 B | A | view · diff |
| v2.0.0 | 2026-03-25 | 0ab0a60 | 3,216 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3842 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
product-on-purpose/pm-skills · 790 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_usw5sno24vnlooxc GET https://markdownregistry.com/api/v1/resolve?ref=product-on-purpose/pm-skills/develop-solution-brief GET https://markdownregistry.com/api/v1/blob/0cb3407abb6f61a8647b2b78718c943e3a8004c6f83fdb362890bbce12c24f10
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.