agentleFS
Sign inStart free
rvdbreemenrvdbreemen/adr-kit/skills/retire/SKILL.md

retire

Skill13 starsChanged 4 months agoMITView on GitHub

Rank Accepted ADRs for retirement. Use for stale decisions, removed technology, supersession signals, or ADR cleanup. Read-only.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use $ARGUMENTS as the ADR directory.

    line 13
  2. Distinctive:

    Run the bundled deterministic scanner from the project root:

    line 21
  3. Distinctive:

    Do not modify ADR statuses or status histories during this audit.

    line 40
  4. Very specific:

    Treat MONITOR as an observation, not as proof that an ADR is obsolete.

    line 41

≈ “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

adr-kit retire

Reply in the language the user writes in; default to English. Keep command output, identifiers, paths, and ADR file content unchanged.

Use $ARGUMENTS as the ADR directory; default to docs/adr/ when it is empty.

You are running /adr-kit:retire. This is a read-only audit of Accepted ADRs that may no longer describe the project accurately.

Procedure

  1. Resolve the ADR target from the optional argument; default to docs/adr/.

  2. Run the bundled deterministic scanner from the project root:

    python <adr-kit-plugin-path>/bin/adr-retire <target> \
  --repo-root . --threshold 0.4 --format markdown
  3. Present every returned candidate with its four signal scores: staleness_90day, tech_removal, broken_supersession, and policy_mismatch.
  4. For any REVIEW or RETIRE result, ask the user whether the decision is actually obsolete, then offer /adr-kit:grill --revalidate ADR-NNN. Revalidate changed forces, remaining implementation, new evidence, and human intent before choosing unchanged, successor, reject-candidate, or defer. Keep this audit read-only until the user confirms a separate lifecycle command.

Boundaries

  • Do not modify ADR statuses or status histories during this audit.
  • Treat MONITOR as an observation, not as proof that an ADR is obsolete.
  • A retirement recommendation is evidence for review, not permission to remove an Accepted decision silently.

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