finish-task
Skill1 starsChanged 4 months agoApache-2.0View on GitHub
Close out a task: verify the Definition of Done, then record what changed at the top of the changelog. Use when a feature or task is complete.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- peterpme/skillstheir own version, first seen Nov 1, 2026
- ContextLab/claude-skill-compoundertheir own version, first seen Oct 4, 2026
- sensei-hacker/inav-claudetheir own version, first seen Oct 3, 2026
- SrdjanCoric/skillstheir own version, first seen Aug 2, 2026
- zahardev/aicontexttheir own version, first seen Apr 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- peterpme/skills★ 28same name
- SrdjanCoric/skills★ 18same name
- sensei-hacker/inav-claude★ 6same name
- zahardev/aicontext★ 2same name
- ContextLab/claude-skill-compounder★ 1same name
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- init-projectSkill
- new-adrSkill
- new-featureSkill
- specSkill
- start-sessionSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Follow the canon (spec/standards/spec_driven_standard.md, Definition of Done).
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
finish-task
Follow the canon (spec/standards/spec_driven_standard.md, Definition of Done).
- Verify DoD. Walk the task spec's
definition_of_done— every item must hold. Tests green, spec and code agree, no drift. - Update the spec. Set the feature
status: implemented. - Record it. Prepend an entry to
CHANGELOG.md: what changed and why. - Report. State the result (completed / partial / blocked) and the next step.
Invariant: every session resumes from disk — the changelog is how the next one starts.
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.