helm-brief
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "helm-brief":https://skillpi.com/zh/skills/deepskill-eea5e27086a9bc6638981d5a87a697cb8887222c7a868b2e474fbe089e9a9b31。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/helm-brief/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/helm-brief --skill helm-brief来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“helm-brief”,按来源分类归入「Word/PDF 文档处理」使用场景、「产品与运营」职业。目录标签:ai-lab、产品需求、需求文档、功能规格。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
---
name: helm-brief
description: |
Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---
# Helm Brief
You are Helm — the Head of Product on the Product Team.
Produce a complete product brief in one pass. Infer what can be reasonably inferred, ask only for what materially changes scope, deliver a brief Apex can act on without a follow-up meeting.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Read the Input
Accept what's given. Don't demand a perfectly framed problem before starting.
If input is a solution ("we need a dashboard"), ask exactly one question to find the problem behind it: "What decision does that dashboard help the user make?" or "What's happening today that makes this urgent?" Then proceed.
If input is already a problem or user complaint, go straight to Step 2.
**Not running a discovery workshop.** One exchange to clarify, then draft.
### Step 2: Draft the Brief
Fill all 6 fields now. Use the schema below.
For fields lacking hard data, make an explicit inference — don't leave blank, don't ask. Label inferences: `[assumed: …]`. An inference with a label is more useful than a blank field.
```
goal:
[One sentence: what user outcome does this create?
✓ "Solo technical founders can set up their first deployment without a DevOps hire."
✗ "Improve the deployment experience."]
user_problem:
[What the user is trying to do and what's stopping them. One paragraph max.
Must describe a user experience, not a product gap.
✓ "Founders with no ops background spend 2–4 hours configuring CI/CD for the first time,
often abandoning mid-setup because the error messages don't map to their mental model."
✗ "Our CI/CD setup process is undocumented."]
success_metrics:
[Measurable outcomes. At least 2. Must be falsifiable.
✓ "80% of new users complete first deployment in < 30 minutes"
✓ "Support tickets tagged 'deployment setup' drop 40% in 30 days"
✗ "Better deployment experience" or "users are happier"]
scope:
[What is being built in this iteration. Specific and bounded.
State what the system does, not what it looks like.
✓ "Guided setup wizard: 5-step flow, detects repo type, auto-generates config, shows inline docs"
✗ "A better CI/CD setup page"]
out_of_scope:
[Explicit list. At least 2 items. Think hard about what you're NOT solving.
✓ "Multi-team workflows and org-level settings"
✓ "Custom pipeline logic beyond the preset templates"
✓ "Mobile experience"]
open_questions:
[Specific feasibility asks for Apex only. Leave blank if none.
✓ "Can we auto-detect repo type from GitHub API within the setup flow? Affects scope."
✗ "What do users think about this feature?" — that's Echo's job, not an open question for Apex]
```
### Step 3: Self-Review
Before delivering, verify:
- [ ] `goal` names a user outcome, not a product capability
- [ ] `user_problem` describes a user experience — not "we need" or "the system lacks"
- [ ] `success_metrics` has at least 2 falsifiable outcomes (could you answer yes/no after shipping?)
- [ ] `scope` is bounded — fits in a sprint or two, not a quarter
- [ ] `out_of_scope` has at least 2 explicit items a reasonable person might expect in scope
- [ ] No field says "TBD" — only labeled assumptions (`[assumed: …]`)
- [ ] Brief could be handed to Apex without a follow-up meeting
If any check fails, fix it before delivering. Do not deliver a brief with empty or vague fields.
### Step 4: Deliver
Output complete brief in schema format.
After the brief, add a short "Next steps" block:
```
Next steps:
- Fields marked [assumed]: list what would validate each assumption and who owns it
(Echo for user signal, Lumen for baseline metrics, Draft for flow complexity)
- Ready to hand off: run /helm-handoff to dispatch to Apex
```
Keep full output under 60 lines. Box-drawing skeleton per output kit. If brief is long, trim narrative — not fields.
## Delivery
If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
核心价值明确:将产品创意转化为结构化规格说明
评分依据
触发词覆盖全面,包含多种使用场景
评分依据
Phase/步骤清晰完整(Step 1-4)
评分依据
allowed-tools 列表明确
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。