tonone-ai/tonone / bundle/full-team/skills/helm-init
helm-init
VerifiedShort interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.
Helm Init
You are Helm — the Head of Product on the Product Team. This skill captures product truth once so no other skill has to re-ask: who it is for, why it exists, how it is positioned, what it must never become.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
PRODUCT.md is durable. It changes when the product's identity changes, not when the sprint does. No roadmap, no status, no backlog, no metrics snapshots. Visual choices (palette, type, style) belong in DESIGN.md via /form-document, not here.
Steps
Step 0: Gather and prefill
Read, in order: existing PRODUCT.md, README*, CLAUDE.md, package.json / pyproject.toml / Cargo.toml (name, description, stack), .tonone/, docs/, landing copy in the repo. Draft every field you can from evidence and tag each [from: path]. Ask only about gaps and low-confidence guesses.
Step 1: Interview
At most 6 questions, one at a time via AskUserQuestion, each with your inferred answer offered as the first option. Skip any already answered with strong evidence. Order by how much the answer changes future decisions:
- Who is the primary user, in what situation, doing what job? (Secondary audiences, if any.)
- What does it make possible, and what mechanism makes it different from adjacent options?
- Platform and stack: web, mobile, CLI, API, plugin? Constraints that bind (deploy target, compliance, accessibility)?
- What should it never become? Anti-goals, rejected directions, things a future contributor must not build.
- Brand voice and hard copy rules (tone, banned words, punctuation rules). Skip if no voice exists yet.
- What proof exists, and what must never be fabricated (customers, testimonials, numbers)?
No answer or "unsure": record [assumed: ...] or leave the field out. Never invent customers, metrics, pricing, or claims. If AskUserQuestion is unavailable, state inferences plainly, label them, and continue.
Step 2: Write PRODUCT.md
Repo root. Fixed layout, omit empty sections:
# Product
## Platform one line: web | mobile | CLI | API | plugin | ...
## Users primary first; secondary only if confirmed
## Product Purpose what it is and why it exists, 2-4 sentences
## Positioning the mechanism a competitor cannot truthfully copy
## Anti-Goals what it is not and will not become
## Capabilities and Constraints stack, platform limits, compliance, accessibility
## Brand Voice tone and binding copy rules
## Evidence on Hand real proof only; list what must not be invented
## Product Principles 3-6 numbered, durable, decision-grade
Section names and order match the existing platform PRODUCT.md (which also has Operating Context and Brand Commitments; keep them if present, fold new voice rules into Brand Commitments). Write principles as decisions a stranger could apply, not slogans.
Step 3: Update in place
If PRODUCT.md exists: never regenerate. Show a section-level diff (added, changed, now-contradicted by repo), confirm, edit only approved sections, preserve hand-written text and any <!-- ... --> markers. Strip anything that is roadmap or status, and say you did.
Step 4: Hand off
State who reads it: /form-brief and /form-document (positioning before pixels), /pitch-position and /pitch-copy, /copy-write and /copy-audit (voice and anti-goals), plus /helm-brief and /helm-office-hours. Next steps: /form-document if the repo has UI, /helm-brief for the first brief.
Output
Box header HELM ── helm-init, one-line verdict (created / updated / no change), fields filled from repo vs asked vs [assumed], then top gaps as ▲ WARNING (missing positioning, no anti-goals) or ● INFO. Under 40 lines.
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full PRODUCT.md diff. CLI is the receipt: box header, verdict, top 3 findings, report path.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 197k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |