write-ticket
Skill10 starsChanged 8 days agoMITView on GitHub
Write a ticket in a dkitchen kitchen — a new GitHub issue, a sub-ticket for one run, or the brief that dispatches an executor. Use whenever a role opens or rewrites a ticket.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- spencerldixon/skillstheir own version, first seen Nov 8, 2026
- Beskars-Code/Skillstheir own version, first seen Nov 6, 2026
- Gabriel-Lafrance/Skillstheir own version, first seen Nov 6, 2026
- nandorszentpeteri/agent-skillstheir own version, first seen Jun 19, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- spencerldixon/skills★ 4same name
- Beskars-Code/Skills★ 0same name
- Gabriel-Lafrance/Skills★ 0same name
- nandorszentpeteri/agent-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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-nightSkill
- build-repoSkill
- build-runnerSkill
- build-teamSkill
- goodmorningSkill
- goodnightSkill
- improve-kitchenSkill
- setup-dkitchenSkill
- shift-changeSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
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
- Very specific: line 10
Write in the repo's language and its ticket layout: the Writing tickets section of the repo's docs/agents/issue-tracker.md, with the words …
- Distinctive: line 39
Check the draft, and fix what fails:
- Distinctive: line 41
every Problem point has its evidence.
- Distinctive: line 42
every exit condition is judged by a number or a command.
- Distinctive: line 43
Leave alone is written;
“Common” is measured: kept by at least 6 in 10 of the 4 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
Write a ticket
A ticket is the only way work is handed out. The executor that picks it up is a fresh session that knows nothing but the ticket and the repo, so the ticket must let it do the work, and let the designer rule on the result, without asking anyone what was meant.
Write in the repo's language and its ticket layout: the Writing tickets section of the repo's docs/agents/issue-tracker.md, with the words from its .dkitchen.toml.
1. Gather
- The decision behind it: the user's words or the designer's ruling, verbatim, with its date and link.
- The evidence: each incident or measurement the problem rests on, with its link and its number.
- The landing points: the files and functions the change touches, read on the current
main, not from memory. - Neighbouring tickets: those that must finish first, and those that change the same files and so must run one after the other.
Done when every claim you will make has a link, a number, or a file and line behind it.
2. Write each part
- Title: what changes, in the repo's own terms, so the change is clear from the title alone.
- Second line: the design line that owns the ticket and the reviewer of its PR. Watches and design lines route the ticket by this line.
- Approval: the user's words quoted verbatim with their date, when a user decision is the ticket's origin.
- Depends on: the tickets that must finish first, and why.
- Problem: what goes wrong today, one point per incident, each with its evidence. The problem, not the fix.
- Do: the behaviour to reach and where it lands. Write decisions, not options. Write the rules and limits that apply in full, since the executor never sees policy messages sent to other roles. Write model-visible text verbatim. Where the work needs a judgment halfway, write a checkpoint: "explore, then wait for the designer".
- Leave alone: what must not change even when it looks related, such as interfaces, running jobs, or other tickets' files.
- Exit conditions: each one judged by reading a number or running a command, never by taste: a test that passes, a count against a threshold, an offline replay that matches. The executor turns them into its gate table, row for row and in this order.
- Footer: the tier and budget when the ticket runs models, who executes, and the role that answers questions on the ticket.
A parent ticket holds the design, rulings, and summary. Each run gets a sub-ticket (ding new --parent <ticket>), written the same way and scoped to that run.
Done when every part the layout names is written, or removed because it does not apply.
3. Check and post
Check the draft, and fix what fails:
- every Problem point has its evidence;
- every exit condition is judged by a number or a command;
- Leave alone is written;
- the tier and budget are written when the ticket runs models;
- the role that answers questions is named;
- nothing the work needs lives only in this conversation;
ding check-refs <draft.md>reports no wrong reference.
Then post it with gh issue create --title … --body-file <draft.md> and give the link. Change a posted ticket's body with ding rule <ticket> <draft.md> --edit-body --base <current body>.
Done when the ticket is posted and every check passed.
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.

