Turn a vendor request into measurable must-haves, constraints, evaluation evidence, and owner approvals.
Instructions your experts follow when using this skill.
Write the brief before comparing vendors.
Capture the current process and cost, users and volume, outcome, deadline, budget status, data involved, systems touched, locations, support needs, implementation effort, exit needs, and success measure.
Classify each requirement:
MUST — failure blocks the stated outcome or a named owner requires it;SHOULD — material value with a workable alternative;COULD — useful but not part of the decision;OUT — not in this purchase.Each must or should has a test: document, live demonstration, reference, sample output, security review, or contract term. Avoid vague labels such as enterprise-ready or easy to use.
Ask for the same currency, term, quantity, unit price, minimums, implementation, support, usage charges, taxes, price changes, renewal, notice, termination, data export, and exit cost.
Return the brief, evaluation table, evidence request, and named approvers. The brief does not approve a budget or invite a vendor until the request owner agrees.
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.