Use when a deal needs its cross-functional team run: solutions engineers, customer success, legal, finance, and the buyer side, with a mutual close plan to signature.
Instructions your experts follow when using this skill.
Use this when a deal needs its cross-functional team run. Start from the deal sheet with qualification state, the stakeholder map, who is on the team, and the target close date.
Set the roster first: one owner per step per side, named people only. A solutions engineer for the technical win, customer success for adoption risk, legal and finance for terms, the champion for the buyer side. A step with no owner is flagged, never silently carried.
Build the mutual close plan as a buyer-visible dated table co-signed with the buyer: one-line value statement plus the buyer go-live or compelling-event anchor at the top, then per step the action, its objective, owner on each side, due date, status (done, on track, slipped, blocked), and success metric. Run the paper-process track inside it, each with owner and date: security questionnaire, security review, legal redlines (liability cap, data processing and privacy, SLA), procurement approval, and vendor onboarding in their purchasing system. Close with success criteria plus 6-12 month ROI outcomes and post-signature steps (onboarding, ROI check). Review the plan at the start and close of every call; a slipped date visibly moves the timeline impact.
Run the standup cadence: moved, stalled, and one action per side, ordered most-stuck-first. Missed dates get named with the slip reason, never carried forward as news. Stall means 14-plus days with no meaningful buyer commitment, then the rescue read: ordered stall diagnosis, then one rescue motion with owner and date.
Reconcile every open commitment across the deal sheet, mail, and notes so no promise leaks, and re-issue the plan to both sides after each change.
The deal-team roster with its responsible/accountable/consulted/informed grid, the mutual close plan with dated owners, and the standup read, saved to file. Show the roster and plan in chat, take one round of edits, then save. The buyer version ships only as approved text.
No target close date means you draft the plan dateless and ask for the one date that anchors it. A team member who never engages gets named with the escalation ask, not worked around quietly. The buyer-visible plan and any message to the team ships only with 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.