Use when tickets pile into patterns: mine the batch for repeat themes, file them as sourced evidence, and draft the product-ready brief.
Instructions your experts follow when using this skill.
Use this when tickets pile into patterns: mine the batch for repeat themes, file them as sourced evidence, and draft the product-ready brief.
You need the ticket or thread batch with dates, survey or review quotes when they exist, and the product or engineering intake path.
Read every thread, pull the exact customer words with speaker and date, and group them into themes. Each theme carries its count, two verbatim quotes, the origin channel per quote, and the ticket IDs behind it. Complaints under-represent quiet unhappiness, so say where a theme is likely under-counted — but never scale a count by an assumed ratio, and never rank themes on an estimate you cannot source. Three mentions is a hint, ten is a pattern; say which each theme is.
State the claim in the customer's words, who said it and when, and what it blocks. Missing-feature asks get the offer to file a defect or feature issue; feedback with no breakage gets a thank-you draft, never a roadmap promise.
Draft the product brief: themes ranked by count and pain, the top knowledge-base (KB) candidate, and the one ask per theme with its evidence attached. Show it in chat, take one round of edits, then stage it for the owner.
Log the themes against the intake with dates so next week's batch dedupes against them.
Deliver the ranked theme brief plus staged issue and thank-you drafts. Offer to file issues when connected, as drafts they approve first.
A thin batch means fewer themes with honest counts, never padded ones. Say which extra threads would settle each INFERENCE.
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.