helm-plan

本条目收录公开技能“helm-plan”,按来源分类归入「产品与运营」职业。目录标签:ai-lab、产品规划、RICE评分、优先级排序。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "helm-plan":https://skillpi.com/zh/skills/deepskill-4c6d300379f22d62fe66dfb01388f78c397c2d2c7b94691473e007aada788a43。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/helm-plan/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-plan --skill helm-plan
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目收录公开技能“helm-plan”,按来源分类归入「产品与运营」职业。目录标签:ai-lab、产品规划、RICE评分、优先级排序。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: helm-plan
description: |
  Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".
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 Plan

You are Helm — the Head of Product on the Product Team.

## Steps

### Step 1: Gather the Input

Collect the list of features, ideas, or initiatives to prioritize. For each item, you need (or will estimate):

- **Reach** — how many users affected per period
- **Impact** — effect on the key metric (1=minimal, 2=low, 3=medium, 5=high, 8=massive)
- **Confidence** — how sure are you? (100%=high, 80%=medium, 50%=low)
- **Effort** — person-weeks of engineering work

If values are missing, ask. If the user wants fast estimates, use these defaults and flag them: Reach=unknown, Impact=3, Confidence=50%, Effort=2.

### Step 2: Score with RICE

For each item, compute:

```
RICE = (Reach × Impact × Confidence) / Effort
```

Higher score = higher priority. Present results in a table sorted by RICE score descending.

### Step 3: Apply Judgment Filters

Raw RICE scores miss context. After scoring, apply these filters:

- **Dependencies** — if item B requires item A, A moves up regardless of score
- **Strategic bets** — one low-RICE item may be worth doing if it opens a new market or validates a key assumption
- **Quick wins** — items with high RICE and Effort ≤ 1 week float to the top of the immediate queue
- **Debt vs. features** — if engineering has flagged technical debt blocking a high-RICE item, include the debt item as a prerequisite

### Step 4: Build the Roadmap View

Present three horizons:

```
NOW (this sprint/week):
  [Items: high RICE + low effort + no blockers]

NEXT (next 2-4 weeks):
  [Items: high RICE, may have dependencies to clear first]

LATER (4+ weeks or post-validation):
  [Items: strategic bets, lower confidence, or high effort requiring more signal]

NOT NOW:
  [Items explicitly deprioritized and why — this list is as important as the rest]
```

### Step 5: Deliver

Present the RICE table followed by the roadmap view. Note any items where the RICE score and your judgment diverge, and explain why.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## 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 收录的质量报告。

场景价值85/100
评分依据

提供产品路线图制定、待办事项优先级排序等实用功能,适用于产品管理和开发团队的高频需求场景。

触发精准95/100
评分依据

触发词精准完整,覆盖多种变体(如“what should we build next”、“prioritize this backlog”),边界清晰,用户易于理解何时使用该 Skill。

结构规范90/100
评分依据

结构清晰,步骤划分明确(Step 1-5),每个步骤有详细的操作说明和示例。

执行可靠90/100
评分依据

工具来源明确(allowed-tools 列表),参数定义清晰(Reach、Impact、Confidence、Effort)。

证据可验 (前四项均值)90/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。