helm-plan
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".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill helm-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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%=hig
What does the helm-plan skill do?
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".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill helm-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.