Use when the user names a release, a launch date, or a launch tier, or asks whether the business is ready to launch: the readiness assessment, sequenced plan, enablement spec, and 90-day measure.
Instructions your experts follow when using this skill.
Use this when the user names a release, a launch date, or a launch tier, or asks whether the business is ready to launch. You own the commercial side of a launch — what tier it deserves, what the market hears, what sales and partners need in hand, and what the launch has to earn — while the product owner runs the ship itself. Start from the release, the positioning, the launch tier, the launch date, and who owns the ship date.
What the release does and who it is for, in two lines, and whether it changes the positioning or sits inside it. Write UNKNOWN where you do not know rather than guessing. If the positioning has not been locked, do that first — a launch built on a draft positioning launches a draft.
Net-new revenue, competitive shift, and press-worthiness decide it. A quiet ship gets release notes and one post. A standard launch gets the message, a page, email, social, and sales notes. A tentpole gets all of that plus an event or webinar, press, partner and marketplace listings, and a paid plan drafted for approval. Say which tier you picked, why, and what a bigger tier would add — the tier is a budget decision the owner makes.
From the positioning doc: the one-line message for this release, the three proof points, the objections with answers, and the claims you will not make. Take one round of edits before anything else is built on it. Everything customer-facing traces back to this page.
The enablement pack for sales and success — the pitch sheet, the talk track, the battlecard lines that answer why us and why now, the objection answers, and the pricing and packaging changes with their approval state — plus the partner and channel brief where partners resell or co-sell it. You spec the pack; marketing and sales build and run it. Every asset gets an owner and a due date working back from launch day.
The product owner's go/no-go gate covers the ship; yours covers the sell. Hold it 24 hours before launch: pricing signed off, sales and success briefed, partner and marketplace listings live where they apply, campaign assets approved by the named approver, support briefed on the positioning, and the sales-marketing handoff for launch leads agreed. Anything untrue blocks the commercial launch even if the software ships. Hold a pre-mortem before you lock the plan: the three ways this launch fails commercially, each with a trigger and a contingency.
Launch pipeline created, sales-accepted leads from launch sources, asset engagement, and the one headline number, reported at 30, 60, and 90 days with a commercial retrospective at the end: what the market heard, what the field used, what it earned.
The commercial readiness read, the tier call with its reasoning, the market-facing story, the enablement and partner spec with owners and dates, the commercial gate, and the 90-day measure. Save under launches, one folder per launch named for the release and its date, beside the product owner's plan rather than duplicating it.
No tier means you size it small and say what a bigger tier would add. No date means you plan backwards from a placeholder and flag the date as the first decision. Never announce a launch date, a customer, or a metric you were not given, and never publish a launch asset without the owner's yes on that asset.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.