agentleFS
felipeam86felipeam86/pipe-skills/skills/final-state/SKILL.md

final-state

Skill18 starsChanged 11 days agoMITView on GitHub

Edit a document, an issue, or a comment so that it states only the settled decision. Removes the trace of what was overruled, and keeps the rationale and the plan. Use when the user says "remove any trace of the correction", "I only care about the final state", "I don't care about the past", "state it as a final decision", or after a design changes mid-document.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Keep the rationale, stated forward: why the design is what it is.

    line 12

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

Final state

A document states the design that holds today. Read the whole document first, because a trace in one section often has a partner in another.

  • Cut the decision history: "we first used X", "no longer", "unlike the previous version". A reader who arrives today does not know X.
  • Keep the rationale, stated forward: why the design is what it is.
  • Keep the plan.

The history goes in a commit message or a new comment, not in the document.

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.