跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 develop-solution-brief

Develop Solution Brief

创建一个简明的一页解决方案概览,以传达拟议办法、关键决定和取舍。 在向利益攸关方投放解决方案时使用,使团队在方法上保持一致,或在详细说明之前记录解决方案意图.

703 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

创建简明的一页解决方案概览,介绍拟议办法、关键决定和取舍

何时用

- 向利益攸关方提供解决办法,以获得接受

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Solution Brief、When to Use、When NOT to Use、Instructions、Output Format、Quality Checklist。 其中含规范建议的小节:输入输出示例。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/TEMPLATE.md、references/EXAMPLE.md,属于带资源的技能包,这些文件按需再读。

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

Solution BriefWhen to UseWhen NOT to UseInstructionsOutput FormatQuality ChecklistExamples

· 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
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.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 2
  • references/TEMPLATE.md
  • references/EXAMPLE.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「develop-solution-brief」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c4fec47638a5fc42-%E5%BC%80%E5%8F%91%E8%A7%A3%E5%86%B3%E6%96%B9%E6%A1%88%E7%AE%80%E4%BB%8B.html
请存为 .cursor/skills/develop-solution-brief/SKILL.md 或 .claude/skills/develop-solution-brief/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/product-on-purpose/pm-skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/product-on-purpose/pm-skills' --list

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

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- 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 version: "2.1.0" updated: 2026-06-10 category: ideation frameworks: [triple-diamond, lean-startup, design-thinking] author: product-on-purpose --- # 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) - 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: 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. 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.

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…