Use when top alliances need a global executive forum: charter the council, run regional-to-global cadence, and drive every decision to an owner.
Instructions your experts follow when using this skill.
Use this when top alliances need a global executive forum. Start from the council alliances, the executive roster on both sides, the charter (or the decision to write one), trailing metrics and milestones, and the last council's minutes where they exist.
Purpose, the member roster with named executive sponsors per side and per region, decision rights (what the council can actually commit), cadence, the communications plan (who hears what, and when), minutes kept per session, the reporting line to the board, and the bar for escalating into it.
One charter document, both sides signed, with a periodic charter-review clause — purpose, roster, and rights revisited at least annually.
A council with no named sponsor per side does not meet until it has one.
A global session per cycle, with regional lead-ins that feed it. One shared partner scorecard carrying metrics plus qualitative health, reviewed define-measure-analyze-improve-control style, and per-metric red/yellow/green bands set per metric rather than one global default.
Regional reads roll into the global pack. No region re-litigates its numbers live.
Revisit council composition annually, and map the handoffs at each alliance inflection point — deal to execution, launch to scale, scale to exit — so the right people own each phase.
A champion co-drafted agenda, the pre-read to members three business days out, wins and misses with their reasons, and the decisions needed stated up front.
The pack follows the executive-review shape — value, gaps, roadmap, asks — with every number sourced.
Recap with decisions, owners, and due dates inside 24 hours. Debrief with the champion inside a week.
An open-decisions log with an owner and a due date per item. A mid-cycle nudge on anything drifting. A stalled item escalated to the sponsors with one rescue motion.
Open the next session on last cycle's log. An undone item carries its reason forward; it never silently drops.
The signed charter, the regional-to-global cadence, the session pack with its pre-read and recap, and the open-decisions log.
No roster yet means drafting the charter with sponsor seats marked UNKNOWN for the owner to fill. No trailing metrics means the first session sets the metric set and its bands, marked provisional.
No charter, pack, or recap goes to a partner executive or a council member without your explicit 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.