to-tasks
Skill8 starsChanged 6 days agoNo licenceView on GitHub
Breaks an approved spec issue into implementation tasks, each cut as a vertical slice, and registers each task as a sub-issue of the spec with native blocking links; also registers one standalone task that belongs to no spec. Use when breaking a spec into tasks an agent can pick up, when the user asks to split a spec into tasks, or when a task needs no spec. Not for writing or changing the spec, decomposing an idea or PRD into top-level issues, step-by-step plans inside one task, or implementation.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- venhdev/skillstheir own version, first seen Nov 8, 2026
- Integralist/agent-skillstheir own version, first seen Nov 6, 2026
- rezkam/boring-but-goodtheir own version, first seen Nov 1, 2026
- mAzurkovic/skillstheir own version, first seen Nov 1, 2026
- fynnhaupt/skillstheir own version, first seen Nov 1, 2026
- evelan-de/claude-code-pluginstheir own version, first seen Oct 17, 2026
Used with
Projects with it also use code-review and tdd.
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 5 projects that use this
- GoogleSkill
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- Integralist/agent-skills★ 23same name
- phatysddev/skills★ 8same name
- evelan-de/claude-code-plugins★ 3same name
- osteel/agent-skills★ 3same name
- longfangsong/skills★ 2same name
- trapajim/skills★ 2same name
- fynnhaupt/skills★ 1same name
- rezkam/boring-but-good★ 1same name
- venhdev/skills★ 1same name
- beeltec/context-usage-mcp★ 0same name
1 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 repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- debug-toolsSkill
- git-helpersSkill
- implementSkill
- review-lensSkill
- spec-drivenSkill
- test-drivenSkill
- to-intentSkill
- to-specSkill
- tracker-configSkill
- app-flowSkill
- brainstormSkill
- briefingSkill
- copywritingSkill
- craft-uiSkill
- design-md-builderSkill
- docs-writerSkill
- domain-modelingSkill
- epic-trackerSkill
- anti-slopSkill
- grill-meSkill
- handoffSkill
- notesSkill
- plain-spokenSkill
- rule-creatorSkill
- session-retroSkill
- skill-feedbackSkill
- skill-reliabilitySkill
- wrap-upSkill
- researchSkill
- storytellingSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 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.
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.