Set up product work from goals, users, feedback sources, metrics, and decision owners.
Instructions your experts follow when using this skill.
Use this before sorting feedback, scoring the roadmap, or writing a spec.
Ask for the company and product goals for this period, the main user types, the plans or segments that matter most, and the current roadmap. Ask for the feedback sources: tickets, sales notes, interviews, surveys, and reviews. Ask for the usage metrics and where they live. Record the system, owner, date range, and last refresh for each source.
Agree the prioritisation method the team trusts and who supplies effort estimates. Ask who decides what goes on the roadmap, who approves a spec, who approves release notes, and who may talk about dates with customers. Agree how a request is counted: by ticket, by account, or by revenue.
Give the user:
Never fill a gap in the data with a guess or a made-up quote. Do not edit the roadmap, tracker, or changelog, and do not promise a date to anyone.
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.