product-team

Plugin product-team from marketplace tonone-ai in tonone-ai/tonone. Commands read from the repo's manifest — 2 days ago.

Skills (83)

• buzz-community

  Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program

• buzz-launch

  Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".

• buzz-pitch

  Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".

• buzz-recon

  PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.

• buzz-social

  Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".

• copy-slop

  Run the deterministic copy-slop check on drafts or UI strings: AI-tell words, residue, em-dash and contrast-frame overuse, with waivers for client terms. Use when asked to "check for AI slop", "does this sound like AI", "run the slop check", or "lint this copy".

• crest-compete

  Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".

• crest-narrative

  Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".

• crest-okr

  OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".

• crest-recon

  Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap

• crest-roadmap

  Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".

• cut-fetch

  Fetch licensed real photos and icons by subject, with credits recorded. Use when asked to "find a photo of", "get an icon for", "fetch stock imagery", or "source real assets". Local files only, per-asset licence record, refuses unclear licences.

• deal-close

  Close a specific deal — diagnose why a deal is stalling, answer an objection reply, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", "help me get to yes", or "how do I answ

• deal-pipeline

  Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".

• deal-playbook

  Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".

• deal-pricing

  Design pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".

• deal-recon

  Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".

• deal-signals

  Signal-based prospecting — read target companies' public sites for buying signals (ads, incumbent agency, tech stack, hiring) with evidence URLs, then build a cohort. Use when asked to "find buying signals", "profile these companies", "which accounts should we target", or "build a target list from t

• draft-flow

  Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this

• draft-ia

  Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hi

• draft-recon

  UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wirefra

• draft-review

  Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".

• draft-wireframe

  Wireframe a screen — buildable ASCII spec by default (Form and Prism can act on it), or a hand-drawn single-file HTML whiteboard look when the user says "sketch", "hand-drawn", "lo-fi HTML", or "visual wireframe".

• echo-feedback

  Feedback synthesis — cluster support tickets, NPS verbatims, app reviews, and churn surveys by theme into an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", or "NPS analysis".

• echo-interview

  Run a user interview — produce an interview guide and synthesize output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", or "build a persona from this feedback".

• echo-jobs

  Jobs-to-Be-Done analysis — from a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", or "why are users switching".

• echo-panel

  Synthetic stakeholder panel — grounded personas react to a launch, pricing change, PRD, or message; returns ranked objections and messages to test. Use when asked to "simulate how users will react", "test this launch with a synthetic panel", "focus group this", or "pressure-test this message".

• echo-recon

  User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or

• echo-segment

  User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".

• form-audit

  Use when asked to audit UI for visual quality, design consistency, brand alignment, or design system compliance before launch. Examples: "audit our UI", "check visual consistency", "is our UI on-brand", "design QA before launch".

• form-bolder

  Make a timid design bolder. Use when asked to "make it bolder", "more punch", "too safe", or "it looks generic".

• form-brand

  Use when asked to create a brand identity, define visual direction, generate a color palette or type system, or build a style guide. Examples: "create a brand for X", "define the visual identity", "what colors should we use", "build a style guide".

• form-brief

  Translate a design brief (I-Lang or plain English) into a concrete DESIGN.md and optional HTML token preview, resolving palette, typography, layout, mood and density to CSS tokens. Use when asked to "create a design brief", "write a DESIGN.md", "design brief for X", or "I-Lang brief".

• form-component

  Use when asked to design a UI component, specify a button, input, card, modal, badge, or any interactive element. Examples: "design a button component", "spec out the input field", "define the card component states", "create a component spec for Prism", "what should the dropdown look like".

• form-critique

  Expert 5-dimension design critique, scored 0-10 with a punch list. Use when asked to "critique this design", "expert review", "score my design", "design feedback", or "review this UI". Unlike /form-audit (technical consistency QA), this judges craft. Isolated reviewer plus detector evidence. "as a r

• form-deal

  Deal a pre-vetted palette and type pairing for a trade and page kind, avoiding recent picks. Use when asked to "deal me a palette", "pick a starting palette and fonts", "re-deal", or "form-deal". A starting deal, not a verdict.

• form-deck

  Use when asked to design a pitch deck, presentation, or slide set. Examples: "design a pitch deck", "create a sales deck", "make a conference presentation", "build an investor deck", "help me present this to the board", "create slides for X".

• form-direction

  Design direction advisor: generates 3 differentiated visual directions with live HTML demos. Use when the brief is vague ("make something nice", "pick a style", "explore directions") or no design system exists. Richer than /form-style: real demos, not just recommendations. Also "design direction", "

• form-distill

  Strip a design to its essence. Use when asked to "simplify this", "distill it", "too cluttered", or "cut it down".

• form-document

  Derive or refresh DESIGN.md from shipped code and tokens, not intentions. Use when asked to "document the design system", "write DESIGN.md", or "refresh DESIGN.md". Frequency-ranks real values, flags one-offs as drift, diffs instead of overwriting.

• form-email

  Use when asked to design an email template, newsletter, drip campaign email, transactional email, or any HTML email asset. Examples: "design a welcome email", "create a newsletter template", "make an onboarding email sequence", "design a password reset email", "build an email campaign".

• form-lint

  Deterministic design lint for UI code — mechanical checks for AI-slop patterns, contrast, tiny text, token drift. Use when asked to "lint the design", "design lint", "check for AI slop", or "run form-lint". Taste rules are advisory; Form and the human decide.

• form-logo

  Use when asked to create a logo, design a brand mark, generate a logo concept, or produce any logo asset. Examples: "create a logo for X", "design a brand mark", "make me a logo", "generate logo concepts", "logo for our product".

• form-mobile

  Use when asked to design iOS or Android mobile app screens, create mobile UI, spec mobile flows, or produce screen designs for a native app. Examples: "design the onboarding screens", "spec the checkout flow for iOS", "design a home screen for Android", "create mobile UI for this feature".

• form-polish

  Final polish pass on a finished UI. Use when asked to "polish this", "final pass", "tighten it up", or "last details before ship".

• form-quieter

  Tone down a loud, noisy design. Use when asked to "make it quieter", "too busy", "calm it down", or "it feels overwhelming".

• form-social

  Use when asked to design social media graphics, ad creatives, or marketing assets. Examples: "design a LinkedIn post for our launch", "create ad creatives for our campaign", "make an Instagram story", "design a Twitter card", "create a banner ad", "social assets for the product announcement".

• form-tokens

  Use when asked to define a design token system, create or document tokens, set up CSS custom properties, build a Tailwind token config, or establish a spacing scale. Examples: "set up design tokens", "define our token system", "create CSS variables", "document our color tokens".

• form-web

  Design a landing page or marketing website that converts or informs. Use when asked to "design a landing page for X", "create a marketing site", "we need a homepage", "design our website", or "build a page for our launch".

• helm-arbiter

  Scope arbitration — resolve product-vs-engineering disagreements on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "scope is creeping", or "help us decide what to cut".

• helm-autoplan

  Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.

• helm-brief

  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".

• helm-handoff

  Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this

• helm-init

  Short 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-office-hours

  Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.

• 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".

• helm-recon

  Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", or "orient me on this product".

• ink-calendar

  Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".

• ink-case

  Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".

• ink-post

  Write a blog post or article — research the keyword, draft the post, and produce publish-ready content with SEO optimization. Use when asked to "write a blog post", "write about [topic]", "draft an article", or "write a tutorial".

• ink-recon

  Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to "audit our content", "what's our SEO state", "where are the content gaps", or before designing a content strategy.

• ink-seo

  SEO audit and keyword strategy — find real search opportunities and recommend the 1-3 changes most likely to grow converting organic traffic. Evidence-first; unknown metrics stay unknown. Use when asked to "improve our SEO", "do keyword research", "audit our SEO", or "why aren't we ranking".

• keep-expand

  Design expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to "grow existing customers", "increase NRR", "design upsell", or "how do we get customers to expand".

• keep-health

  Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model".

• keep-onboard

  Optimize customer onboarding — map the activation sequence, identify drop-off points, design the aha moment, and produce the onboarding email sequence. Use when asked to "fix onboarding", "improve activation", "time-to-value is too slow", or "customers aren't getting started".

• keep-playbook

  Write churn prevention and win-back playbooks — risk intervention sequences, save conversation guides, and win-back email campaigns. Use when asked to "prevent churn", "save at-risk customers", "win back churned customers", or "build a save play".

• keep-recon

  Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.

• lumen-abtest

  A/B test design — experiment spec with hypothesis, primary metric, MDE, sample size, run time, decision rule; also says when NOT to A/B test. Use when asked to "design an A/B test", "should we test this", "experiment design", or "what's the sample size".

• lumen-funnel
• lumen-instrument
• lumen-metrics
• lumen-recon
• move-moments
• pitch-copy
• pitch-launch
• pitch-message
• pitch-position
• pitch-recon
• surge-activation
• surge-experiment
• surge-plg
• surge-recon
• surge-retention

Subagents (12)

• buzz

  PR & Community engineer — press pitches, social media, open source community, DevRel, and coordinated launch moments

• crest

  Product strategist — diagnosis-first strategy, roadmap sequencing, competitive positioning, and market decisions

• deal

  Revenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing

• draft

  UX designer — user flows, information architecture, wireframes, and interaction design

• echo

  User researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis

• form

  Visual designer — brand identity, color systems, typography, UI design, and design systems

• helm

  Head of Product — product strategy, requirements, and engineering handoff via the Helm↔Apex interface

• ink

  Content Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar

• keep

  Customer Success engineer — onboarding optimization, health scoring, expansion revenue, churn prevention, and NRR growth

• lumen

  Product analyst — metrics architecture, funnel analysis, A/B test design, retention, and growth measurement

• pitch

  Product marketer — positioning, messaging, value proposition, GTM strategy, and launch copy

• surge

  Growth engineer — acquisition channels, activation funnels, retention playbooks, and PLG strategy

Hooks (1)

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/team/form/hooks/form-design-lint.js"

Similar plugins