tickets
Skill1 starsChanged 37 days agoMITView on GitHub
Turn one section or phase of a spec into small, ordered tickets (at most ~5 files each) with acceptance criteria, Files, dependencies and a milestone, and create them in the issue tracker and on the project board. Use when planning the next phase of work from a spec. Part of the dev-flow lifecycle.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- Birdiz/skillstheir own version, first seen Nov 16, 2026
- andymai/claude-agent-teamtheir own version, first seen Nov 16, 2026
- andymai/skillstheir own version, first seen Nov 15, 2026
- jeremy-farnault/claude-skillstheir own version, first seen Nov 3, 2026
- phnx-labs/.agentstheir own version, first seen Oct 11, 2026
- jasonhulbert/skillstheir own version, first seen Oct 9, 2026
Used with
Projects with it also use interview, spec and 1 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.
dazuckSkillinterview
Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.
Also in 3 projects that use this
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 5 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
- gregwebs/skills-sdlc★ 21same name
- andymai/claude-agent-team★ 4same name
- andymai/skills★ 4same name
- toverux/cantrips★ 3same name
- Birdiz/skills★ 2same name
- garthcodes/claude-skills★ 2same name
- jasonhulbert/skills★ 1same name
- phnx-labs/.agents★ 1same name
- Thalisu/SKILLS★ 1same name
- eric-wien/ogma★ 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 repository14 other files it gives its agents.
- skills/setup-project/templates/AGENTS.mdAGENTS.md
- grill-meSkill
- addressSkill
- conventional-commitsSkill
- design-packageSkill
- doneSkill
- implementSkill
- preview-prSkill
- researchSkill
- setup-projectSkill
- stop-previewSkill
- takeSkill
- ui-from-referenceSkill
- visual-notesSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Survey: Search the code for files the section touches.
“Common” is measured: kept by at least 6 in 10 of the 11 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 <spec section> [milestone]
Project facts live in AGENTS.md. Read it, then only the named spec section and .github/ISSUE_TEMPLATE/ticket.md.
- Survey. Search the code for files the section touches. Note what already exists.
- Slice. Draft tickets in dependency order. Each one is a vertical slice that ships alone in one PR:
- at most ~5 files, testable on its own, one observable result;
- title
<area>: <outcome>(e.g.briefs: import a pasted brief); - body from the template: Goal, Acceptance (checkboxes a reviewer can verify), Files (mark new ones), Depends (draft numbers), Reference (spec §, design screen), Out of scope.
- UI work and its logic are separate tickets when together they pass ~5 files.
- Confirm. Show one line per ticket: number, title, file count, depends. At most 12 per batch. Wait for "go" or edits.
- Create in order, replacing draft numbers with real ones as you go:
gh issue create --title "<title>" --body-file <tmp> --label status:todo --milestone "<milestone>" --project "<project title from AGENTS.md>" - Report the numbers and titles.
Shortest complete answer. End with one line: Next: /take on <model for take in AGENTS.md>.
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.

