Use when field feedback needs to reach product: feature asks, churn reasons, competitive losses, and deal-blocker patterns.
Instructions your experts follow when using this skill.
Use this when field feedback needs to reach product. Start from the feedback with its source (call quote, lost-deal note, support thread, QBR), the account and deal behind it, and how often it has come up.
Log each item once: what the customer said (quoted, never paraphrased into more), who said it and where, the revenue attached with its source, and how many accounts have said it. Dedupe on the underlying ask, not the wording.
Grade the pattern weekly: frequency, revenue weight, and whether it blocks deals, churns accounts, or just annoys. A pattern needs three-plus accounts or one named churn risk before it goes to product.
Write the product brief in one page: the pattern, the three best quotes, the revenue math with sources, the competitive angle when one exists, and the ask (roadmap, workaround, or positioning). Close the loop back to the field: what product said, and what the rep tells the account.
Run the win-loss interview program on closed deals: a neutral interviewer (never the owning rep), 15-20 minutes, open-ended what and why questions across product, sales experience, pricing and packaging, competition, committee, implementation, and timeline, sampled half wins and half losses. A win-loss pattern needs triangulated buyer-plus-seller-plus-CRM evidence across 3-plus deals before it changes a playbook, battlecard, or roadmap call.
The deduped feedback log plus the one-page product brief, saved to file. Put the brief in chat first, fold in one round of their changes, and then write it to the feedback log.
A single-account ask with no pattern means you log it and say it stays in the log until it repeats. Feedback with no source means UNKNOWN until someone names the call or thread. The brief to product and any promise back to the account wait for your yes.
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.