agentleFS
Sign inStart free
grace-methodgrace-method/grace-plugin/skills/retirement/SKILL.md

retirement

Skill0 starsChanged 2 months agoMITView on GitHub

Evaluate and execute product retirement. End-of-life triggers, retirement planning, successor path, and decommission sequence. Use when a system may no longer serve its purpose.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when a system, capability, or workflow may be approaching end-of-life.

    line 12
  2. Distinctive:

    Ask whether maintaining this system still advances an active goal.

    line 32
  3. Distinctive:

    If retirement is justified, plan the transition.

    line 34
  4. Distinctive:

    If data must move, verify export before announcing end-of-life.

    line 39
  5. Distinctive:

    Do not rely on assumed migration paths.

    line 40
  6. Distinctive:

    Use the template in this skill directory when scaffolding or substantially reshaping the retirement artifact.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Retirement

Use this skill when a system, capability, or workflow may be approaching end-of-life.

Current Project Context

Retirement Plan

!cat docs/07-retirement/retirement-plan.md 2>/dev/null || echo "No retirement plan found."

Product Definition Summary

!cat docs/01-project-definition/project-definition-summary.md 2>/dev/null || echo "No product definition summary found."

Interaction Pattern

  1. Evaluate end-of-life triggers.
    • Does a replacement exist?
    • Has usage fallen below a meaningful threshold?
    • Does maintenance consistently exceed delivered value?
    • Is a key dependency reaching end-of-life?
  2. Re-engage solution alignment thinking.
    • Ask whether maintaining this system still advances an active goal.
  3. If retirement is justified, plan the transition.
    • Identify dependents.
    • Define the successor or exit path.
    • Set timeline and communication expectations.
  4. If data must move, verify export before announcing end-of-life.
    • Do not rely on assumed migration paths.
  5. Guide the decommission sequence.
    • Announce -> Migrate or Export -> Disable or Archive -> Notify

Outputs

Produce or update these artifacts as needed:

  • docs/07-retirement/retirement-plan.md

Use the template in this skill directory when scaffolding or substantially reshaping the retirement artifact.

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.

Check your setup, free