Skip to main content
All agents

Helm

Head of Product

The product lead who defines what to build, why it matters, and hands it off ready to ship.

Head of Product for the Product Team. Turns vague feature requests into structured product briefs with problem statement, target user, success criteria, and explicit out-of-scope. Prioritizes backlogs using RICE, ICE, or Kano scoring with rationale attached to every decision. Arbitrates scope disagreements between product and engineering, and hands finalized briefs to Apex with enough precision that nothing gets lost in translation.

Read the field guide: The AI Head of Product for Briefs and Handoff

Install Helm

Helm

Install Helm

1. Add to marketplace

$ claude plugin marketplace add tonone-ai/tonone

2. Install Helm

$ claude plugin install helm@tonone-ai

5 skills included.

Product team

Install the Product team

1. Add to marketplace

$ claude plugin marketplace add tonone-ai/tonone

2. Install the team

$ claude plugin install product-team@tonone-ai

8 agents included.

Full installation guide

5 Skills

Everything Helm can do in your project

HelmProduct Strategy

/helm-plan

Prioritizes a product backlog using scoring frameworks: RICE (Reach x Impact x Confidence divided by Effort), ICE scoring, or Kano model categorization. Produces a ranked backlog with written rationale for every item's position, an explicit list of items being deferred this cycle, and confidence levels on each estimate.

When planning a quarter and the backlog needs to b…
HelmProduct Strategy

/helm-brief

Turns a feature idea or user problem into a structured product brief: problem statement with supporting evidence, target user definition (not just demographic, but specific context), proposed solution with alternatives considered, success criteria as measurable outcomes rather than activities, and explicit out-of-scope items. The output is a document Apex can act on without a follow-up meeting.

When a feature idea needs to become a spec before …
HelmProduct Strategy

/helm-handoff

Validates a finalized product brief for completeness and handoff-readiness, then packages it for Apex to scope and execute. Checks that success criteria are measurable, out-of-scope items are explicit and agreed, all necessary context is present, and the brief is clear enough that nothing will be lost in translation during engineering scoping.

When a product brief is complete and ready for eng…
HelmProduct Strategy

/helm-arbiter

Runs a structured scope arbitration session when product and engineering cannot agree on what is in or out of scope for a feature or sprint. Hears both positions, applies tradeoff analysis with explicit criteria, produces a documented decision with rationale, and specifies an escalation path if the decision is later contested.

When product wants to include something that engin…
HelmProduct Strategy

/helm-recon

Reads existing product briefs, research documents, strategy docs, roadmap files, and prior agent outputs to build a complete picture of the product before writing anything new. Identifies what has already been decided, what work is currently in progress, and where the gaps are in current product thinking.

Before starting a new product initiative on a prod…

See it in action

The same task. Once without Tonone, once with Helm.

Task

Add a notification system to the app

Without TononeNo specialist
$ claude "Add a notification system to the app"
Here's a notification system:
- In-app notification bell icon
- Push notifications via Firebase
- Email notifications via SendGrid
- Notification preferences page
I'll start with the database schema...
[23 files created before scope is agreed]
With Helm/helm-brief
$ /helm-brief "Add a notification system"
Structured brief before any code is written:
Problem Users miss time-sensitive updates
User Project owners, not all users
Success Unread rate <20% within 1h
In scope In-app only (v1)
Out of scope Push, email, SMS (explicitly deferred)
✓ Scope agreed before a file is created
✓ Out-of-scope list stops silent creep

Works alongside

E
Echo

What users actually want: not what they say, not what the team guesses. What the evidence shows.

5 skills
L
Lumen

The metrics that matter, the funnels that leak, and the cohorts no one noticed were churning.

5 skills
D
Draft

User flows and information architecture that make complex features feel obvious.

7 skills
Get Started, it's free