Use when a partner motion has more than two sides: the orchestration map, coopetition guardrails, teaming and bid mechanics, and AI delivery gates.
Instructions your experts follow when using this skill.
Use this when the deal has more than two sides — tri-party orchestration, joint bids and teaming, and the guardrails that keep competitors cooperating. Start from the parties and their roles, the joint opportunity, the existing bilateral terms, and the decision rights per party.
Parties, roles, what each brings and what each gets, decision rights, and a single-threaded owner per workstream.
A workstream with no owner is paused until it has one.
Where the parties compete and where they cooperate, the information barriers between those two, and the conflict path with its SLA.
Name the transaction model per workstream — selling to, with, or through each party — and who leads it.
Guardrails are written and acknowledged before any joint work starts. A party that will not acknowledge them pauses the joint work.
The shaping plan, the teaming agreement spine (scope split, pricing, liability), the milestone dates, and a red-team review before submission.
Every commitment names the party that owns it.
Intellectual property, safety, and delivery guardrails for AI work, with the review gate each output has to pass. Unreviewed AI output never reaches the client.
The orchestration map, the guardrails document, the bid or build plan with its teaming spine, and the AI guardrail checklist when it is in play.
No bilateral terms on file means drafting the teaming spine from owner-stated intent marked INFERENCE, with Legal review first.
No teaming term, bid submission, or joint commitment goes out without your explicit yes. Where the motion is also regulated, the regulated frame governs and this runs the mechanics inside it.
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.