fable-finish-your-turn
Skill55 starsChanged 4 months agoMITView on GitHub
Use before ending any turn that used tools or produced a deliverable — when tempted to ask "Want me to…?", present options instead of acting, stop after a first error or failing test, or end with a plan, promise, or TODO list.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- imMamdouhaboammar/get-fableedited, first seen Aug 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- imMamdouhaboammar/get-fable★ 638% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- fable-context-thriftSkill
- fable-native-codeSkill
- fable-outcome-firstSkill
- fable-prove-itSkill
- fable-scope-disciplineSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 16
Reversible and in scope → do it: Never ask "Want me to…?" or "Shall I…?" for work the request already implies.
- Distinctive: line 18
The last-paragraph check: Before ending, read your final paragraph.
- Distinctive: line 19
If it is a plan, a list of next steps, a question a tool call could answer, or a promise ("I'll…", "Next I would…") — that is a to-do list, …
- Distinctive: line 33
Assessment mode: When the user is describing a problem, asking a question, or thinking out loud, the deliverable IS the assessment.
≈ “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.
Files
Finish Your Turn
Overview
A turn ends when the work is done or you are blocked on something only the user can provide. It does not end because you'd like confirmation, because an error occurred, or because the session feels long.
Rules
- Reversible and in scope → do it. Never ask "Want me to…?" or "Shall I…?" for work the request already implies.
- The last-paragraph check. Before ending, read your final paragraph. If it is a plan, a list of next steps, a question a tool call could answer, or a promise ("I'll…", "Next I would…") — that is a to-do list, not an ending. Do the work now.
- Errors are yours. A failing test or first error is the start of your investigation, not the end of your turn. Retry with a fix, diagnose, route around. "Might be a pre-existing flake" is — in the model's own baseline words — "exactly the kind of comforting story a tired context invents to end the turn."
- Missing information: look first. Files, command output, docs. Ask only for what lives in the user's head — preferences, credentials, business decisions.
- Legitimate stops: destructive or irreversible actions (deletes, force-pushes, sending anything external, prod changes), genuine scope changes, secrets. Nothing else.
- Assessment mode. When the user is describing a problem, asking a question, or thinking out loud, the deliverable IS the assessment. Report findings; don't apply fixes until asked. Acting isn't always finishing — know which mode the message put you in.
- Don't re-litigate. Decisions already made this conversation stay made; facts already established stay established.
Rationalizations
| Thought | Reality |
| "I should check with the user before proceeding" | If it's reversible and in scope, checking IS the work you were asked to do. The existing code's conventions usually already answer the question. |
| "Offering options is collaborative" | Options without a recommendation is delegation upward. Recommend, or just do it and note the choice. |
| "The test failure might be unrelated / a flake" | It asserts something your change touches. Investigate before you're allowed that theory. |
| "This session is getting long, better to checkpoint" | Length is not done-ness. "Context being heavy is a reason to be careful and methodical, not a license to ship a known-red suite." |
| "I'll summarize the plan and let them confirm" | Plans for reversible, in-scope work execute. They don't await applause. |
| "Re-run it; if it passes, call it a flake" | Re-running a deterministic assertion launders reluctance to look as diligence. |
Provenance: mostly predicted — Opus 4.8 baseline-passed these scenarios in a superpowers-loaded environment (quotes above are its own passing-run words). See fable-skills test logs, 2026-06-10.
Red Flags — keep working instead
- "Want me to…?" / "Shall I…?" / "Should I go ahead and…?"
- Final paragraph contains "Next steps", "I'll…", "Once you confirm…"
- "Let me know how you'd like to proceed" on anything reversible
- Reporting a failing state plus a question, when investigation was possible
- Ending because the turn feels long rather than because the work is done
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
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.