to-issues
Skill8 starsChanged 43 days agoNo licenceView on GitHub
Turn new user stories and acceptance criteria, usually from to-prd, into task-breakdown cards (backend, frontend, and a wiring card where the seam needs one) added to docs/task-breakdown/, then file one issue per card the way github-project-init does, with the role's assignee, labels, sprint milestone, board status, and estimate, each linked to the parent issue. Use when the user wants to break a feature or PRD into issues or tickets on a project that is already running.
130 other projects use a version of this.
Adopted by
Most recently taken up by
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- kazemcodes/skill-treetheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use decision-mapping, modern-go and 10 more.
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.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 7 projects that use this
jidechaoSkillmodern-go
Modernize Go code by applying version-appropriate idioms and APIs (gofix-style transformations). Scans go.mod for the Go version, then transforms Go source files to use modern patterns—from Go 1.0 through 1.26+. Use when the user says "现代化","现代Go语言", "地道的", "idiomatic", "modernize", "modern-go", "update Go code", "gofix", or wants to upgrade Go idioms.
Also in 3 projects that use this
victorgarciaesgiSkillzoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
Also in 49 projects that use this
- jidechaoSkill
loop-it
Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → document with /note-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现, 实现所有issue, 恢复循环, resume loop.
Also in 3 projects that use this
simo97Skillrequest-refactor-plan
Use this skill when user wants to create a refactor plan.
Also in 18 projects that use this
- simo97Skill
edit-article
The user will invoke this skill to help them edit an article.
Also in 18 projects that use this
- +2 more from jidechao
- +2 more from simo97
Other versions130 projects use a version of this.
Word for word · 1
- snowfluke/tech-lead-skills★ 8100% same
Edited · 0
None found.
Wrote their own version · 129
- GreyDGL/PentestGPT★ 16ksame name
- bholmesdev/hubble.md★ 1.5ksame name
- DanMcInerney/architect-loop★ 626same name
- amazingloft999-droid/mattpocock-skills★ 422same name
- Tiberriver256/mcp-server-azure-devops★ 399same name
- smallnest/goal-workflow★ 283same name
- ninehills/skills★ 280same name
- InditexTech/weavejs★ 266same name
- serejaris/personal-corp-os★ 243same name
- serejaris/ris-claude-code★ 243same name
119 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.
- adopt-flowSkill
- api-specSkill
- coding-standardSkill
- deployment-planSkill
- github-project-initSkill
- groomingSkill
- init-claudeSkill
- lead-reviewSkill
- product-discoverySkill
- project-docsSkill
- security-standardSkill
- task-breakdownSkill
- tech-lead-setupsSkill
- technical-specSkill
- test-auditSkill
- to-prdSkill
- triageSkill
- troubleshootingSkill
- us-ac-formatterSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 122 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
7
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 122 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.