Use when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
Instructions your experts follow when using this skill.
Use this when partners deliver client work in your name. Start from the in-flight engagement book (partner, client, scope, dates, staffing), the delivery status per engagement, the escalation history, and the client success criteria.
One row per engagement: partner, client, scope, milestone dates, the staffed team, and a red/yellow/green delivery grade with one line of evidence behind it. A grade with no evidence stays UNKNOWN.
The book is rebuilt weekly from the tracker, never from memory.
Most-at-risk first, one decision per engagement: on track, needs support, restaff, or escalate.
Before any escalation, build the peer map — functional peers with equal decision authority on both sides — and escalate peer-to-peer first.
A staffing gap gets a dated restaff line with an owner. Anything red two weeks running gets an executive escalation draft.
Name the failure mode — staffing, skill, scope, or client-side — pick one save motion with a date, and log it.
A third straight red week triggers the save-or-exit call with its evidence attached.
A per-partner delivery-quality read: on-time rate, escalation count, client satisfaction. It feeds the portfolio review and the renewal call, so delivery shows up in the commercial decision rather than beside it.
The graded engagement book, the weekly review log with its decisions, the active rescue plans, and the quarterly delivery-quality read.
No tracker means building the book from owner-pasted status notes marked INFERENCE, with standing up the tracker as the first action. No success criteria means drafting them from scope and confirming with the owner.
No staffing change, escalation, or client-facing message goes out 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.