tickets
Skill4 starsChanged yesterdayMITView on GitHub
Split a plan, a spec, or the current conversation into tickets. Each ticket is a vertical slice and names the tickets that block it.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- andymai/skillsword for word, first seen Nov 15, 2026
- 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
Used with
Projects with it also use spec, implement and 4 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.
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
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 4 projects that use this
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
GoogleSkillgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
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
- +1 more from google
Other versions11 projects use a version of this.
Word for word · 1
- andymai/skills★ 4100% same
Edited · 0
None found.
Wrote their own version · 10
- gregwebs/skills-sdlc★ 21same name
- 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-docsSkill
- handoffSkill
- interviewSkill
- obsidian-projectSkill
- outward-writingSkill
- retrospectiveSkill
- shepherd-prSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 15 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If the line above names a file, an issue, or a URL, read all of it, with its comments.
- Distinctive: line 19
If the line is empty, use the plan in the current conversation.
- Distinctive: line 27
Read the code that the work changes.
- Distinctive: line 31
Look for a prefactor: a change that makes the work easy and changes no behavior.
- Distinctive: line 37
Use the first rule that applies:
- Distinctive: line 42
Ask the user: a tracker, or local files.
- Distinctive: line 44
Do not publish to a tracker that neither the user nor the project named.
- Distinctive: line 72
Expand: add the new form next to the old form.
- Distinctive: line 76
Contract: delete the old form. This ticket is blocked by every migrate ticket.
- Distinctive: line 85
Do you want to merge two tickets or to split one?
- Distinctive: line 92
Use this template for each ticket:
- Distinctive: line 114
Write each acceptance criterion as a result that someone can check.
- Distinctive: line 117
Do not give file paths or code.
- Distinctive: line 120
Use the project's own words for its domain objects.
- Very specific: line 122
Local files: write one file for each ticket, named <NN>-<short-title>.md.
- Distinctive: line 131
If the source was an issue, link each ticket to it as the parent.
“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.
Files
Tickets
Split the work into tickets that an engineer or an agent can do one at a time. Each ticket is a vertical slice: a narrow change that goes through every layer and that someone can verify by itself. Each ticket names the tickets that block it.
The source of the work, if the user gave one: $ARGUMENTS
1. Get the source
If the line above names a file, an issue, or a URL, read all of it, with its comments. If the line is empty, use the plan in the current conversation.
Gate: you can state the goal and what is out of scope in two sentences. If you cannot,
stop. Tell the user that the work is not ready to split, and that /team:interview settles
the open decisions.
2. Read the code
Read the code that the work changes. Find the layers that a feature goes through in this repo (for example: schema, API, UI, tests) by reading one existing feature from end to end.
Look for a prefactor: a change that makes the work easy and changes no behavior. First make the change easy, then make the easy change. A prefactor is its own ticket, and it blocks the tickets that need it.
3. Find where the tickets go
Use the first rule that applies:
- The user's instructions name a tracker or a folder.
- The project's
CLAUDE.mdorAGENTS.mdnames a tracker and its conventions (labels, a template, a project). - Ask the user: a tracker, or local files.
Do not publish to a tracker that neither the user nor the project named. For local files,
use the folder that the user names. If the user names none, use
.scratch/<feature-name>/, and run git check-ignore .scratch to tell the user if git
ignores the folder.
4. Draft the slices
Rules for each ticket:
- It makes one behavior work from end to end, through every layer that the behavior needs. It is not one layer of many behaviors.
- Someone can verify it by itself when it is complete: run it, see it, or test it.
- It fits in one work session for one engineer or one agent.
- It lists its blocked by tickets: the tickets that must be complete before it starts. A ticket with no blocker can start immediately.
Example. The work is "let a user export their orders as CSV".
- Bad (horizontal): "1. Add the export tables. 2. Write the export API. 3. Build the export UI. 4. Write the tests." Nobody can verify ticket 1, 2, or 3 by itself.
- Good (vertical): "1. Export the order ID and the total for one user, from a button on the orders page, with a test. 2. Add the line items to the file (blocked by 1). 3. Send the file by email when the export has more than 10,000 rows (blocked by 1)."
Exception: a wide refactor. One mechanical change (rename a column, change a shared type) can break call sites in all of the codebase, so no vertical slice can pass CI. Do not force it into slices. Use three stages:
- Expand: add the new form next to the old form. Nothing breaks.
- Migrate: move the call sites in batches (one package or one folder in each ticket). Each batch is blocked by the expand ticket. CI passes after each batch, because the old form still exists.
- Contract: delete the old form. This ticket is blocked by every migrate ticket.
5. Show the breakdown and get approval
Show a numbered list. For each ticket, give its title, its blockers, and the behavior that works when it is complete. Then ask the user these three questions:
- Is each ticket the right size, or is one too large or too small?
- Is each blocker correct? Does a ticket wait for a ticket that it does not need?
- Do you want to merge two tickets or to split one?
Change the list and show it again until the user approves it. Gate: do not write a ticket until the user approves the list.
6. Write the tickets
Use this template for each ticket:
# <title that states the change>
## What to build
<The behavior that works when the ticket is complete, as the user of the product sees
it. Not a list of changes for each layer.>
## Acceptance criteria
- [ ] <a result that a person can check with a command or an action>
- [ ] ...
## Blocked by
<each blocking ticket, or "Nothing. This ticket can start immediately.">
## Out of scope
<what this ticket does not do, and which ticket does it>Rules for the text:
- Write each acceptance criterion as a result that someone can check. "The export works" is not a criterion. "A file with 3 orders has 4 lines: the header and one line for each order" is a criterion.
- Do not give file paths or code. They go out of date before someone starts the ticket. The exception is a short snippet that states a decision more exactly than prose: a schema, a type, or a state table.
- Use the project's own words for its domain objects.
Local files: write one file for each ticket, named <NN>-<short-title>.md. Number
from 01 in dependency order, with the blockers first. Before you write, list the
folder. If it has ticket files from an earlier run, do not overwrite them. Ask the user
if you must replace that set or use a new folder.
A tracker: a ticket is prose that other people read. Before you publish, invoke the
team:outward-writing skill with the Skill tool, and follow it for the text of each
ticket. Show the full text of each ticket to the user before you publish it. Publish in dependency order, with the blockers first, so that each ticket can
give the real ID of its blockers. If the tracker has a native "blocked by" link, use it.
If the source was an issue, link each ticket to it as the parent. Do not close or change
the parent issue.
7. Report
- Each ticket with its ID or its path, in dependency order.
- The tickets that can start now (no blocker).
- Anything from the source that no ticket covers, and why.
Final self-check
- Each ticket goes through every layer that its behavior needs, or it is a stage of a wide refactor.
- Each acceptance criterion is a result that someone can check.
- No ticket waits for itself through a chain of blockers.
- Each requirement in the source is in a ticket, or the report says that it is not.
- The user approved the list before you wrote a ticket, and saw each ticket before you published it to a tracker.
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.

