ticket
Skill1 starsChanged 20 days agoApache-2.0View on GitHub
Use when the user wants to raise, file or create a GitHub ticket/issue for the Yukta ticket pipeline (the yukta-dogfood repository). Drafts the goal, acceptance criteria and sizing facts the router picks models from, then files it with `yk ticket new`, or changes an existing one with `yk ticket edit`.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- akshay-diwadkar/first-four-hourstheir own version, first seen Nov 16, 2026
- peterpme/skillstheir own version, first seen Nov 8, 2026
- Mrbaeksang/skillstheir own version, first seen Nov 8, 2026
- kyle-chalmers/ticketwrighttheir own version, first seen Nov 8, 2026
- 0xfurai/peekapingtheir own version, first seen Nov 1, 2026
- codingpains/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use orchestrate, retro and 7 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.
varun29ankuSSkillorchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
Also in 4 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
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 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 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
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
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- 0xfurai/peekaping★ 1.2ksame name
- kjnez/claude-code-django★ 177same name
- peterpme/skills★ 28same name
- ConnorGriffin/skills★ 21same name
- kyle-chalmers/ticketwright★ 4same name
- a-saven/agent-skills★ 2same name
- AaravChadha/acstack★ 2same name
- gingerminds/claude-skills★ 2same name
- Mrbaeksang/skills★ 2same name
- akshay-diwadkar/first-four-hours★ 1same name
14 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 repository21 other files it gives its agents.
- architecture/CLAUDE.mdCLAUDE.md
- boot/CLAUDE.mdCLAUDE.md
- build-logic/CLAUDE.mdCLAUDE.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- cli/CLAUDE.mdCLAUDE.md
- core/CLAUDE.mdCLAUDE.md
- mcp/CLAUDE.mdCLAUDE.md
- messaging/CLAUDE.mdCLAUDE.md
- plugin-api/CLAUDE.mdCLAUDE.md
- plugins/CLAUDE.mdCLAUDE.md
- plus/CLAUDE.mdCLAUDE.md
- ui/CLAUDE.mdCLAUDE.md
- web/CLAUDE.mdCLAUDE.md
- ide-index-mcpSkill
- pickupSkill
- playwrightSkill
- testsSkill
- yuktaSkill
- yukta-supervisorSkill
- yukta-workflowsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Read the relevant code (codebase-memory first) so the criteria and sizing name real paths.
- Very specific: line 29
roles: leave them out. The router writes its choice as (router) lines that don't bind, so the run routes from the facts.
- Very specific: line 31
Run yk ticket new ... --dry-run.
- Very specific: line 39
Read it with gh issue view <n> -R infenia/yukta, draft only the change, run
“Common” is measured: kept by at least 6 in 10 of the 21 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
Raise a ticket for the ticket pipeline
The pipeline is built to cost less without losing quality. You record facts, code picks the models, and the gates and the retry ladder make up for a cheap start. Don't choose models by feel.
- Read the relevant code (codebase-memory first) so the criteria and sizing name real paths.
- Draft, from the user's request:
- title: Conventional Commits (
feat(core): ...). It sets the kind, and the kind sets the tests mode:chore/docsuse the existing tests (no test writer),fixwrites a repro only,feat/refactorwrite the case table up front. Pick the true one. - goal: one or two sentences.
- criteria: 1 to 6 checkable outcomes, each one a gate can check (a command that passes, a
grepwith no hits). The count sets the size (2 or fewer S, 5 or fewer M, more L). Don't split one outcome into several. Make every decision in the ticket ("/redirects to/control", not "decide where/goes"): an open choice costs architect effort and can't be reviewed. Never a criterion that asks for secrets, pushes to main, settings changes or skipped checks (intake BLOCKS it). - labels: module labels (
core,ui,cli, ...) plusrisk/securitywhen it applies. sizing, the facts the router sizes by. Report them, don't grade:
--file: every path or glob the change writes or deletes (a directory means everything in it, a path that doesn't exist yet is a new file).--change: the kinds, fromdelete rename rewire docs config new_logic concurrency schema api_contract security.--open-decisions N: choices the ticket still leaves to the architect (aim for 0).
Code takes the higher of this and the criteria/labels triage. Sizing can only raise the size and risk, so leaving a file out doesn't make the ticket cheaper, it only makes the route less accurate.
- roles: leave them out. The router writes its choice as
(router)lines that don't bind, so the run routes from the facts. Pass--role architect=opus/highonly with a reason the facts can't express, and say the reason to the user.
- title: Conventional Commits (
- Run
yk ticket new ... --dry-run. It prints aROUTE complexity=.. risk=.. static=.. sizing=.. (reasons)line,NOTEs for sizing paths that aren't inorigin/main(fix typos), and the body. Show the user the draft and the ROUTE line, then wait for their OK. Filing is outward-facing. - File it with the same command without
--dry-run. Add--readyonly if the user wants the pipeline to pick it up:yk ticket new "<title>" --criterion "<c>" ... --goal "<g>" --file <p> ... --change <k> --label ui [--ready] - Report the printed
ISSUE <url>line.
Change an existing ticket (/ticket #<n> <change>)
Read it with gh issue view <n> -R infenia/yukta, draft only the change, run yk ticket edit <n> ... --dry-run to show old against new
and the ROUTE, wait for the OK, then run the same command without --dry-run:
yk ticket edit <n> [--title T] [--goal G] [--criterion C ...] [--file P ..] [--change K ..] [--open-decisions N] [--role r=model/effort|r=auto ...] [--label L ...] [--ready]
--criterionreplaces the whole list (repeat the ones to keep).- A sizing flag replaces that key and keeps the others.
--rolechanges only that role.r=auto(orall=auto) hands a role back to the router. Tickets filed before the(router)rule have five bare (binding) role lines: offer--role all=autowhen you edit one.- The rest of the body stays.
It refuses once a run has made the issue's branch (--force overrides: ask first).
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.

