tickets
Skill1 starsChanged 22 days agoNo licenceView on GitHub
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker. Invoke only when the user explicitly asks for it or when /next routes to this stage — never spontaneously.
10 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- andymai/skillstheir own version, first seen Nov 15, 2026
- jeremy-farnault/claude-skillstheir own version, first seen Nov 3, 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 spec and handoff.
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.
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 4 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 versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- toverux/cantrips★ 331% same
Wrote their own version · 9
- gregwebs/skills-sdlc★ 21same name
- andymai/skills★ 4same name
- garthcodes/claude-skills★ 2same name
- BinayakDotel/skills-marketplace★ 1same name
- jasonhulbert/skills★ 1same name
- phnx-labs/.agents★ 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 repository38 other files it gives its agents.
- releaseSkill
- autopsySkill
- codebase-designSkill
- cold-readSkill
- conventionsSkill
- create-verification-skillSkill
- decidingSkill
- designSkill
- diff-reviewSkill
- domain-modelingSkill
- evalsSkill
- finding-pipelineSkill
- grillingSkill
- hitl-questionsSkill
- implementSkill
- issue-trackerSkill
- iterateSkill
- maintain-iterateSkill
- maintain-verification-skillSkill
- model-policySkill
- multiplexerSkill
- nextSkill
- principlesSkill
- prototypeSkill
- researchSkill
- rsiSkill
- seedSkill
- shipSkill
- snagSkill
- specifySkill
- spec-reviewSkill
- tddSkill
- tendSkill
- testingSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
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.