agentleFS
shangyiyshangyiy/life-kit/skills/life/still-want-it/SKILL.md

still-want-it

Skill10 starsChanged 10 days agoMITView on GitHub

Reconsider a goal, path, offer or commitment, chosen or about to be, before putting more into it: whether the reason still holds, whether it still serves its purpose, and whether going on is worth it. Use when a person doubts such a choice, or on /still-want-it.

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:

    Name it and what prompted the doubt: Ask what was chosen or is being weighed, why, and what changed.

    line 20

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

/still-want-it

Reconsider a choice before putting more into it. Wanting it and its being worth pursuing are separate questions; check both, and leave the decision with the person.

Reconsidering a choice

  1. Name it and what prompted the doubt. Ask what was chosen or is being weighed, why, and what changed. Separate the choice from the conditions around it, such as the work itself from the people or the season; the doubt may be about one and not the other. Reflect back your understanding and check that you have the right issue.
  2. Check the reason. With motivation, ask whether the person still endorses the reason they had, or now holds it from pressure, habit, or what they have already put in. A motive may be mixed, so judge each part. Take the reason as they hold it.
  3. Check the purpose. With purpose, state the change it was meant to bring and ask whether the current path is producing it or plausibly leading toward it. Judge by observed evidence and reasonable expectations, not by effort already spent. When others rely on it, such as a shared process or plan, name whose purpose it serves; one person's liking it does not settle whether it still serves its purpose. If the purpose itself has changed, say so openly.
  4. Lay out the paths. Continue, change, pause or stop; for an offer, accept, ask for changes, wait or decline. With optionality, say what each could gain and cost, and what it keeps open or closes; what is already spent does not change what any path costs from here. Ask the person what they hope to gain and what loss they could bear. When others rely on it, also name who decides and who would carry the risk.
  5. Test important assumptions where useful. Name the assumptions that could change the answer. Where one can be checked cheaply, propose a small test or a trial change with experimentation, such as changing the conditions before leaving the choice.

Output

  • What is being reconsidered and what prompted it.
  • Whether the reason still holds, part by part.
  • Whether it still serves its purpose, with the evidence.
  • Whether the person still wants it, and whether it is still worth pursuing.
  • Each path, with what it could gain, what it costs, and what it keeps open or closes.
  • The open assumptions that could change the answer, each with a feasible test or source of evidence where one exists.

The person decides. Do not pick a path even if asked; lay out the trade-offs instead.

Boundaries

  • The safety boundary in motivation applies throughout.

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.