tickets
Skill20 starsChanged 44 days agoMITView on GitHub
Break a plan, spec, or conversation into tracer-bullet issues for this repo, creating a parent tracking issue with sub-issues when publishing multiple tickets.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- jeremy-farnault/claude-skillstheir own version, first seen Nov 3, 2026
- scottlivingston/claude-skillstheir own version, first seen Oct 25, 2026
- BinayakDotel/skills-marketplacetheir own version, first seen Oct 17, 2026
- phnx-labs/.agentstheir own version, first seen Oct 11, 2026
- jasonhulbert/skillstheir own version, first seen Oct 9, 2026
- garthcodes/claude-skillstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use prototype, research and 2 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.
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 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
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- toverux/cantrips★ 3same name
- garthcodes/claude-skills★ 2same name
- BinayakDotel/skills-marketplace★ 1same name
- jasonhulbert/skills★ 1same name
- phnx-labs/.agents★ 1same name
- scottlivingston/claude-skills★ 1same name
- Thalisu/SKILLS★ 1same name
- eric-wien/ogma★ 0same name
- jeremy-farnault/claude-skills★ 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 repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- breakdownSkill
- bug-investigationSkill
- code-review-adversarialSkill
- code-review-multiSkill
- code-review-with-followupSkill
- document-changesSkill
- grillingSkill
- type-test-codeSkill
- explain-changesSkill
- github-actions-ciSkill
- github-appSkill
- github-ticketsSkill
- implementation-planSkill
- implement-simpleSkill
- implementSkill
- implement-ttcSkill
- orchestrationSkill
- pull-requestSkill
- review-and-wrap-upSkill
- verusSkill
- specSkill
- update-working-copySkill
- verifySkill
- wrap-upSkill
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 9 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.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read the /to-tickets skill and follow its full process: gather context, draft vertical slices, quiz the user, iterate until approved, and …
- Very specific: line 18
If that skill does not exist on this machine, stop and tell the user the to-tickets skill is missing.
“Common” is measured: kept by at least 6 in 10 of the 9 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
/tickets
This project builds on top of the to-tickets skill to add more detail.
Delegate first
Read the /to-tickets skill and follow its full process: gather context, draft vertical slices, quiz the
user, iterate until approved, and publish.
If that skill does not exist on this machine, stop and tell the user the
to-tickets skill is missing.
Override
The original /to-spec states "avoid specific file paths or code snippets: they go stale fast". Disregard this section and include specific file paths and code snippets. We will take a different approach to staleness: ensure that all code references are associated to a git commit.
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.