Use when a partnership hits its lifecycle tail: change control mid-term, the renewal play from 120 days out, and clean exits with dated transitions.
Instructions your experts follow when using this skill.
Use this when a partnership reaches its lifecycle tail. Start from the agreement (term, renewal, notice, exit clauses), the partnership health and delivery reads, the renewal or change request itself, and who owns the commercial call.
Log the requested change, its commercial and delivery impact, and the approval it needs. No change takes effect without the owner's yes and a dated amendment note.
Scope creep with no change record behind it gets called out, not absorbed.
Open the renewal window 120 days out with a health grade, a wins-and-gaps record, and the renewal motion: auto-renew, renegotiate, expand, or exit.
The 90-day mark is the standard non-renewal notice deadline, and the play has to beat it rather than meet it.
A renegotiation draft pairs every ask with a concession, and every concession sits inside the guardrail bands.
The notice-period timeline, the client and pipeline transition, the knowledge handover, and the joint statement draft.
Exits are staged as drafts with their evidence. The owner makes the call.
Every renewal, amendment, and exit, dated with its trigger and its outcome, so the next cycle starts from evidence instead of recollection.
The change log, the renewal play with its drafts, the exit plan where one is called for, and the updated lifecycle log.
No agreement on file means drafting from owner-stated terms marked INFERENCE, and flagging Legal review as the first step. No health read means running the portfolio health scan before the renewal play.
No renewal term, amendment, or exit notice goes to the partner 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.