plan-task
Skill0 starsChanged 3 months agoMITView on GitHub
Convert an ambiguous software, data, or agent-workflow request into a bounded task contract with scope, interfaces, constraints, risks, and measurable acceptance criteria. Use before implementation when requirements or success conditions are not already decision complete.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- etr/groundworktheir own version, first seen Nov 8, 2026
- rumotion/ai-agent-project-templatetheir own version, first seen Nov 1, 2026
- griffinhilly/claude-code-synthesistheir own version, first seen Nov 1, 2026
- fitlab-ai/agent-infratheir own version, first seen Oct 27, 2026
- anaidenko/claude-notify-resumetheir own version, first seen Oct 15, 2026
- Yesterday-AI/ytstacktheir own version, first seen Oct 13, 2026
Used with
Projects with it also use ship and 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.
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
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 versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- ModelEngine-Group/fit-framework★ 2.1ksame name
- mattolson/agent-sandbox★ 212same name
- fitlab-ai/agent-infra★ 87same name
- griffinhilly/claude-code-synthesis★ 67same name
- jezweb/vite-flare-starter★ 49same name
- etr/groundwork★ 45same name
- LevNas/ccmemo★ 4same name
- Yesterday-AI/ytstack★ 2same name
- anaidenko/claude-notify-resume★ 1same name
- NAVNAV221/ai-native-codebase★ 1same name
2 more not listed
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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyzeSkill
- buildSkill
- data-pipelineSkill
- handoffSkill
- orchestrateSkill
- plan-taskSkill
- plugin-devSkill
- reviewSkill
- verifySkill
- analyzeSkill
- buildSkill
- data-pipelineSkill
- handoffSkill
- orchestrateSkill
- plugin-devSkill
- reviewSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
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
- Distinctive: line 8
Read available repository instructions, task state, and relevant files.
- Distinctive: line 12
Prefer the smallest design that satisfies the request.
- Distinctive: line 14
If the project defines a durable artifact contract, save the approved plan there.
- Very specific: line 15
When creating a Markdown artifact, reuse assets/artifact.md from this skill if available.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Plan Task
- Read available repository instructions, task state, and relevant files.
- Separate discoverable repository facts from user preferences.
- State the goal, audience, in-scope behavior, exclusions, and constraints.
- Define interfaces, data boundaries, failure modes, tests, and acceptance criteria.
- Prefer the smallest design that satisfies the request.
- Surface any material decision that cannot be derived; do not choose silently.
- If the project defines a durable artifact contract, save the approved plan there; otherwise return it inline.
- When creating a Markdown artifact, reuse
assets/artifact.mdfrom this skill if available.
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.