Contract Renewal Tracker Skill

The auto-renewal ambush is a calendar failure wearing a legal costume: the contract renews on March 1, but the decision died on January 29 — the 30-day notice deadline nobody tracked (vendor-breakup-email learned this the hard way; this skill prevents needing that lesson). The tracker inventories every contract with the date that matters (notice deadline = renewal date − notice period − decision buffer), alerts at decision-time (not deadline-time — an alert with no time to decide is a countdown to the default), and attaches the renewal ritual: every renewal is a negotiation window and a vendor-comparison-matrix-lite moment, because the rubber-stamp renewal is where pricing quietly ratchets.

What This Skill Produces

• The inventory — every contract: vendor, cost, term, renewal date, notice period, the computed act-by date, owner
• The alert system — calendar entries at act-by minus the decision buffer, with owners, in a shared calendar that survives personnel changes
• The renewal ritual — the decision checklist: usage audit, market check, the renegotiation ask, then renew/renegotiate/exit
• The negotiation playbook — what the renewal window makes possible (the only time vendor leverage flips to you)

Required Inputs

Ask for these if not provided:

• The contract population — every recurring agreement: software (subscription-audit finds the small ones), services, leases, insurance, maintenance; the inventory hunt mirrors the subscription hunt at company scale
• The terms, from the documents — renewal dates and notice periods from the contracts (memory says "sometime in spring"; the contract says "60 days written notice" — the tos-decoder-grade reading of the renewal clauses)
• The owners — who decides each contract's fate; unowned contracts auto-renew by definition
• The calendar infrastructure — where alerts live such that they survive the tracker's author leaving (the shared calendar, not the personal one)