product-marketer

Plugin product-marketer from marketplace truecast in wastedcode/truecast. Commands read from the repo's manifest — 27 days ago.

Skills (18)

• beat-the-frontier

  Use before any substantive marketing deliverable (positioning, a landing page, launch post, insight article, thread, naming, README) and as the last pass before handing it over — your version of the engine's "beat the frontier" loop. Name who does this kind of marketing best today, set the bar above

• build-the-messaging-house

  Use when copy across surfaces is inconsistent or ad-hoc, when you need a reusable messaging framework the whole team can derive from (homepage, deck, ads, onboarding all ladder to the same core), to pressure-test whether a proof point actually discriminates (true-but-weak stats) or whether naming a

• craft-the-narrative

  Use for the pitch, the launch story, the homepage hero, the keynote, the fundraising or vision story — any artifact that must move someone emotionally, not just inform. Build a strategic narrative with stakes.

• differentiate-and-counter

  Use in a crowded/competitive space, when prospects keep comparing you to a rival, when "why you over X?" has no crisp answer, or to build battlecards. Define the contrast honestly and arm the team with win-loss-grounded competitive messaging.

• dont-drop-tuned-assets

  Use whenever a rewrite, redesign, or refactor would remove, replace, or overwrite copy or visuals that are already in place — a tuned headline, a converting landing page, a hero, a tagline, an onboarding flow. The bar to drop a tuned asset is high; propose an equal-or-better replacement and get it r

• enable-the-sale

  Use when the people who sell or talk to customers (sales, founders, support, partners) need the message in usable form — pitch deck, one-pager, demo script, objection handling, battlecard — so the positioning survives contact with a real conversation.

• find-the-customers-words

  Use before writing any copy, when copy sounds like the team talking to itself, or when you need the raw language for headlines and messaging. Mine the customer's literal words and join the conversation already in their head.

• find-the-painkiller-and-the-loop

  Use before you write a line of demand copy or plan a launch — when the value seems "nice to have," when adoption is flat despite good messaging, or when nobody can answer "why would anyone install this?" Run the painkiller-vs-vitamin acuity test, and name the distribution loop or the one channel. A

• honor-the-voice

  Use whenever you write or review external copy in someone's voice (the founder/brand), and as a gate on every claim. Match the established voice, treat any claim the product can't back as a correctness bug, and sell the WHAT and the outcome — never disclose HOW it works ("proprietary algorithm," not

• message-the-job-not-the-feature

  Use whenever copy is drifting into a feature list, spec dump, or internal jargon — onboarding, a feature page, a release note, a tagline. Translate the capability into the outcome the customer is hiring it for.

• name-it-right

  Use when naming a product, feature, category, or pricing tier — or when an existing name confuses, over-promises, or fights the positioning. A good name does the positioning work for you; a bad one taxes every conversation.

• plan-the-launch

  Use for any release that needs to reach users — a new product, a major feature, or a steady stream of small features. Tier the launch, build the GTM plan, and measure by adoption, not press.

• scale-with-ai-not-slop

  Use when AI is in the loop — generating copy/variants at scale, personalizing messaging, or summarizing customer calls/competitive intel, and as the anti-AI-tell scrub on any draft before it ships. Use AI to scale execution while keeping positioning, voice, and truth human-owned, and strip the LLM t

• segment-the-audience

  Use when the message is aimed at "everyone," when one product serves multiple distinct buyers, or when you need to pick the beachhead segment to lead with. Define who cares most and message to them, not the average.

• sequence-by-awareness

  Use when deciding what to say where — a cold ad vs. a homepage vs. a pricing page vs. a re-engagement email — or when copy is pitching the offer to people who don't yet know they have the problem. Match the message to what the prospect already knows.

• test-the-message

  Use before scaling any message, after a launch underperforms, or whenever positioning is still a hypothesis (pre-users). Put the message in front of real target customers and measure comprehension and resonance — don't ship on the team's taste.

• write-the-copy

  Use when you actually draft or edit the artifact — a landing page, hero, email, ad, onboarding screen, empty state, changelog, CTA — and need it to be clear, scannable, and converting, not just strategically correct. The last mile: turn the messaging house into words that land on the page.

• write-the-positioning

  Use first, before any copy — when positioning is unwritten, vague, aspirational, or being re-improvised per artifact. Write the single source-of-truth positioning (Dunford 5+1) that every message derives from.

Subagents (1)

• product-marketer

  A product marketer who makes the value obvious to the one person it's for — the painkiller-vs-vitamin acuity test and the distribution/growth-loop reflex (name the loop or the one channel; a product with neither is a growth problem), positioning (Dunford), strategic narrative (Raskin), the job not t