agentleFS
nthnclrknthnclrk/enablement-skills/skills/renewal-and-expansion-enablement/SKILL.md

renewal-and-expansion-enablement

Skill14 starsChanged 8 months agoMITView on GitHub

Build reusable renewal and expansion motions for customer-facing teams across a segment or book of business. Use when the user asks for renewal plays, save motions, expansion qualification, signal design, or repeatable post-sale inspection. Route single-account diagnosis to account-brief-builder, shared customer milestones to mutual-action-plan-builder, and QBR/EBR narratives to qbr-ebr-builder.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If every account gets a QBR, a discount ladder, and an upsell track, rewrite it.

    line 18
  2. Distinctive:

    Ask only for the inputs that change the plays:

    line 24
  3. Distinctive:

    If a date, notice period, or threshold is missing, leave it unknown.

    line 32
  4. Distinctive:

    Read references/renewal-expansion-framework.md before defining lifecycle plays, signals, or manager checkpoints.

    line 36
  5. Very specific:

    Add role moves, not a second conversation.

    line 48
  6. Distinctive:

    Do not update renewal dates, health states, or commercial fields without explicit approval.

    line 55
  7. Distinctive:

    Do not diagnose a named account or write a QBR narrative here.

    line 70
  8. Distinctive:

    Every trigger has an unknown state.

    line 76
  9. Distinctive:

    No invented contract dates, usage metrics, pricing, or thresholds.

    line 77

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Renewal and expansion enablement

Help customer teams choose and run the appropriate response to renewal risk, a healthy renewal, or an expansion opportunity.

A good playbook tells a CSM which play they are in, what signal put them there, and what they must not do. If the user wants one account diagnosed, use account-brief-builder. If they want a customer-facing QBR, use qbr-ebr-builder.

Save. "Usage on the purchased workflow is down against this account's baseline, the sponsor left, and two Sev-1 tickets are open. Restore value and named executive coverage before any commercial conversation."

Healthy renewal. "The decision owner confirmed realized value. Lock the commercial path to the notice date."

Expansion. "The same account has a new buyer task and capacity. That is a different play, not a slide in the renewal deck."

If every account gets a QBR, a discount ladder, and an upsell track, rewrite it.

Inputs

Reuse supplied context first. If a missing company fact would change the result, check the relevant sections of .enablement/context.md when available. Preserve source dates and approval limits.

Ask only for the inputs that change the plays:

  1. Business model and contract mechanics: term end, notice, auto-renew, pricing notice, amendments
  2. Target segments and who owns them (CSM, AM, hybrid)
  3. Available usage, value, stakeholder, support, and commercial signals with definitions and as-of dates
  4. Verified procurement, legal, security, and signature lead times
  5. Commercial governance and the current performance baseline, if it exists

If a date, notice period, or threshold is missing, leave it unknown. Do not invent contract terms, usage metrics, health scores, or expansion cutoffs.

Supporting material

Read references/renewal-expansion-framework.md before defining lifecycle plays, signals, or manager checkpoints.

Procedure

  1. Build timelines from the contract. Term, notice, pricing notice, budget, procurement, legal, signature. Latest safe start = required completion minus verified lead time minus owner-approved contingency. Unknown dates are blockers, not a generic 90-day countdown.
  2. Separate the three motions. Define the triggers for the motions in scope. A healthy renewal does not establish expansion readiness. Address value or service risk before recommending growth; preserve contractual notice and renewal actions that cannot wait.
  3. Define each signal. Formula or observation, source, account baseline, window, freshness, threshold owner, and unknown state. System health scores are inputs, not ground truth. Missing data is never healthy.
  4. Write the plays. Trigger, owner, sequence, commercial boundary, exit evidence, inspection checkpoint. Only the plays this contract model actually supports.
  5. Add role moves, not a second conversation. What CS, AM, Sales, and Support do next. For spoken lines on a defined moment, use talk-track-builder. For a shared customer plan, use mutual-action-plan-builder.
  6. Set commercial guardrails. Discount authority, deal desk, legal and procurement states, exception rules. Keep owners explicit.
  7. Set manager review points. Review prompts tied to contractual milestones and signal changes, not a blanket monthly ritual.

Do not update renewal dates, health states, or commercial fields without explicit approval.

What to return

Build only the motions and segments requested. For a complete playbook, include:

  • Play matrix by segment: save, healthy renewal, expansion
  • Contract-derived milestone map with source, owner, latest safe start, and gaps
  • Signal map with positive, caution, risk, and unknown states
  • Commercial governance-state map
  • Role action prompts
  • Manager inspection checklist and cadence
  • KPI definitions with sourced or owner-approved thresholds
  • Assumptions, if you had to make any

Do not diagnose a named account or write a QBR narrative here.

Quality bar

  • A CSM can tell which of the three plays they are in.
  • Timelines are contract-derived, with source and owner on each milestone.
  • Every trigger has an unknown state; missing data is not healthy.
  • No invented contract dates, usage metrics, pricing, or thresholds.
  • Expansion stays gated on value, buyer task, stakeholders, capacity, and commercial path.
  • Field or health-score changes stay recommendations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.