new-ticket
Skill1 starsChanged 40 days agoMITView on GitHub
Capture a bug, idea, request or follow-up in a minute as a ticket folder in plans/backlog/, without planning or fixing it. Use when the user says "create a ticket", "add this to the backlog", "note this for later" or "open an issue for this", or to record the follow-ups a review, debugging session or implementation leaves undone. Not for work the user wants done now.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dr-zog/plumblinetheir own version, first seen Aug 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dr-zog/plumbline★ 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- deep-reviewSkill
- find-bugSkill
- implement-planSkill
- make-planSkill
- make-roadmapSkill
- plan-pageSkill
- plans-conventionSkill
- research-topicSkill
- save-learningSkill
- ship-workSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 26
Ask the user only if the *what* or the *why* is unclear.
- Very specific: line 33
Add --parent <id> if it belongs to a roadmap.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
New ticket
A ticket records something worth doing later, with enough context that it
still makes sense in a month. Capturing it should take a minute: this is not
planning. When the time comes, the ticket is implemented directly if it is
small, or promoted to a plan with make-plan.
Load the plans-convention skill first. <plans-convention> below stands
for the folder that skill was loaded from.
Steps
Gather the essentials, mostly from the conversation and the code:
- what: the bug, idea or request in one or two sentences;
- why it matters, or what triggered it;
- for a bug: how to reproduce it, expected vs actual behaviour, the error, and where it was seen;
- where in the code, if known (paths, functions);
- how we will know it is done (one to three acceptance criteria).
Ask the user only if the what or the why is unclear. Do not ask about the solution; do not investigate beyond a quick look to get the paths right.
- Check for duplicates:
plans.py list --status backlogand--status in-progress. If an existing ticket or plan already covers it, tell the user and offer to add the new information there instead. - Create it:
python3 <plans-convention>/scripts/plans.py new --type ticket --title "<short imperative title>". Add--parent <id>if it belongs to a roadmap. - Fill
plan.md: Justification with the what, why and reproduction; Plan with a first idea of the fix only if one is already known; the acceptance criteria. Leave Implementation, Results and Closure empty. Write in English. - Report the id and path in one line.
Several follow-ups at once (for example, the unfixed findings of a review) are one ticket each, unless they are the same change in several places.
Title
Short and imperative, describing the outcome: "Fix crash when exporting an empty note", "Support dark mode in settings". Not "Bug", "Idea about export", or a sentence copied from an error message.
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.