mcpField
C
contract-lifecycle-renewal-review

contract-lifecycle-renewal-review

github.com/sylphxaiMarketing & growth139 installsUpdated today
Repository

About contract-lifecycle-renewal-review

contract-lifecycle-renewal-review turns contract lifecycle questions into renewal operating plans with owners, gates, metrics, and recovery paths for teams handling commercial contracts. It distinguishes renewals, expansions, downgrades, cancellations, true-ups, and disputes, and calls for reconciling contract, billing, entitlement, and support records.

Key features

  1. 01Classifies contract stage and account situation
  2. 02Defines renewal calendars and health signals
  3. 03Maps approvals, quoting, and billing handoffs
  4. 04Sets entitlement-change gates and exception policies
  5. 05Produces state machines, risk lists, and owner action plans

Use cases

  1. 01Assigning owners and dates for renewal or cancellation
  2. 02Handling expansion, downgrade, or usage true-up
  3. 03Reconciling mismatched billing and entitlement records
  4. 04Planning renewal-risk response and recovery

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill contract-lifecycle-renewal-review

After installing, type/contract-lifecycle-renewal-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/contract-lifecycle-renewal-patterns.md

Details

From the project README

Contract Lifecycle Renewal Review

Use this skill to convert contract lifecycle, renewal, expansion, cancellation, true-up, amendment, procurement, billing, and entitlement questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify customer segment, contract type, term dates, renewal notice window, auto-renewal rule, pricing model, entitlements, billing source of truth, legal owner, and customer-success owner.
  2. Read references/contract-lifecycle-renewal-patterns.md.
  3. Classify the account as new contract, active term, renewal-ready, renewal-risk, expansion, downgrade, cancellation, true-up, dispute, or post-term reconciliation.
  4. Define renewal calendar, health signals, commercial approvals, quote/order/invoice handoff, entitlement change gate, customer communication, cancellation path, and exception policy.
  5. Produce renewal operating plan, state machine, decision table, event schema, risk checklist, and owner-by-date action list.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not rely on surprise auto-renewal, hidden cancellation windows, or dark-pattern retention to protect revenue.
  • Do not change entitlements from CRM notes alone; reconcile contract, billing, provisioning, and support records.
  • Do not treat usage true-ups, price increases, expansion, and collections disputes as the same workflow.
  • Do not promise renewal terms, credits, cancellations, or legal exceptions without an accountable commercial/legal owner.

Output format

Renewal context:
Audience / source of truth / risk boundary:

Renewal operating plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Renewal, downgrade, cancellation, and true-up handling:
- <trigger> -> <policy, metric, edge case, support note>

Comments

Markdown supported