Use when a partnership fights or fades: deal conflicts, missed commitments, deprioritisation, or churn risk — diagnosis, escalation drafts, save-or-exit.
Instructions your experts follow when using this skill.
Use this when a partnership fights or fades — a deal conflict, a missed commitment, deprioritisation, or churn risk. Start from the partner, what happened with its dates, the agreement terms in play, the executive sponsors on both sides, and what the owner wants the outcome to be.
One line, with its evidence attached:
Label it horizontal (partner against partner) or vertical (partner against us). FACT first, then INFERENCE, then UNKNOWN.
Brief our executive sponsor in three lines. Draft the partner-side escalation note for the owner's yes. Propose the ruling or the remedy with a date on it — a price war gets a minimum-advertised-price option plus an average-deal remedy to choose between.
Keep a conflict log: the issue, both sides, the ruling, the date.
Never override a registration without the owner's yes, and never promise credits, exceptions, or term changes. Those are the owner's to give.
A health score built from activity, pipeline, and sponsorship. The one save motion with an owner and a date. The exit bar if it fails.
A partner below the exit bar gets a clean wind-down, not a slow fade.
Date it, so the warming-or-stalling read on that partnership stays honest next quarter.
The one-line diagnosis with evidence, the staged escalation drafts, the conflict-log entry, and the save-or-exit line.
No sponsor named means you ask for one before drafting any escalation — an escalation with no sponsor behind it is just a complaint. Nothing partner-facing leaves without 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.