task-planning
Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub
Create or update durable task documents and implementation plans intended for review, handoff, coordination, or continued execution. Use when the user explicitly requests a task doc or when the work requires a persistent planning artifact. Do not use for the agent's own execution planning, tool-call sequencing, status checklists, or small plans that can be handled with update_plan or a short chat response.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- NoobyGains/godmodetheir own version, first seen Nov 1, 2026
- microsoft/amplifier-app-papercliptheir own version, first seen Oct 25, 2026
- mustafahasanain/frappe-workflowtheir own version, first seen Oct 8, 2026
- LOUSANPANG/agent-skillstheir own version, first seen Sep 2, 2026
- lasp/adamant-skillstheir own version, first seen Aug 13, 2026
- TTflysky/sirenhuisuotheir own version, first seen Aug 4, 2026
Used with
Projects with it also use code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- NoobyGains/godmode★ 118same name
- lasp/adamant-skills★ 4same name
- TTflysky/sirenhuisuo★ 4same name
- zebbern/termstack★ 4same name
- LOUSANPANG/agent-skills★ 2same name
- microsoft/amplifier-app-paperclip★ 1same name
- youjun011/skills★ 1same name
- mustafahasanain/frappe-workflow★ 0same 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 repository4 other files it gives its agents.
- acquire-codebase-knowledgeSkill
- doublecheckSkill
- easy-specsSkill
- verification-before-completionSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
28 rules. 0 are common, 23 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
23
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 6 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.