ticket-plan
Skill1.2k starsChanged 16 days agoMITView on GitHub
Research a Linear ticket, agree a plan with the user, and record it in the ticket.
1 other project uses a version of this.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- rajanrx/skillstheir own version, first seen Nov 8, 2026
Who's talking about 0xfurai/peekaping
- A Hacker News story“peekaping: selfhosted uptime monitoring similar to UptimeKuma (Go/React)”Hacker News · Sep 8, 2025 · 4 points
- ProSkillsMD/proskills“[Candidate] 0xfurai/peekaping/.agents/skills/ticket-review - ticket-review”GitHub · Oct 26, 2026
The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- rajanrx/skills★ 2same 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
- releaseSkill
- ticket-buildSkill
- ticket-loopSkill
- ticket-prSkill
- ticket-reviewSkill
- ticketSkill
- treehouseSkill
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 20
Write the plan from the template in PLAN.md: numbered acceptance criteria, approach, test plan, PR stack, out of scope, follow-ups, open …
- Very specific: line 36
Run alone, end by telling the user the worktree path and the next step: /ticket-build to have Claude implement it, or implement it there …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Ticket: plan
Start with setup.
1. Research
Read the glossary and the ADRs in docs/adr/ that touch the area. Find where the change lands, every caller it affects, the repositories when persistence is involved, and the existing tests at those seams. MongoDB storage was removed (docs/adr/0001-deprecate-mongodb-storage.md): don't plan code that brings it back. The MongoDB monitor type and bun db import-mongo stay. For a bug, reproduce it: a failing test, or a command whose output shows it. Use Explore subagents (effort: "high") for wide sweeps so your context keeps conclusions, not file dumps.
Done when: every requirement in the ticket points at the code it changes and the test seam that will prove it, and a bug is red (seen failing) or you can say why it can't fail locally.
2. Plan
Write the plan from the template in PLAN.md: numbered acceptance criteria, approach, test plan, PR stack, out of scope, follow-ups, open decisions with your recommendation, merge danger.
Done when: every acceptance criterion is checkable and has a test or a stated manual verification, and every PR in the stack is reviewable alone and leaves main green.
3. Checkpoint: agree the plan
Present the brief from PLAN.md, then ask with AskUserQuestion: the open decisions, then approval. Revise and ask again until the user approves. Answers that change scope or approach change the plan text before the next round.
Done when: the user has approved the plan as written.
4. Record the plan in Linear
Append the approved plan to the ticket description as a ## Agent plan section (save_issue with a patch append; on later revisions replace that section only, leaving the reporter's text above it as written). Then save_comment: plan agreed, branch name, PR count.
Done when: the ticket shows the approved plan.
Run alone, end by telling the user the worktree path and the next step: /ticket-build to have Claude implement it, or implement it there yourself and run /ticket <PP-n> from review.
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.

