agentleFS
Prince-VincePrince-Vince/claude-skills/skills/to-tickets/SKILL.md

to-tickets

Skill0 starsChanged 2 months agoNo licenceView on GitHub

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

207 other projects use a version of this, 134 of them edited; 32 of 133 edited versions we compared changed its rules; 10 new projects in the last 4 weeks, against 7 the 4 before.

How people change it

32 of 133 edited versions changed its rules, and some changes recur.

Of the 133 edited versions we compared: 97 keep every rule, 4 are an older text, 32 made changes of their own.

Not in older versions

  1. Do NOT close or modify any parent issue.missing from 4 of 4
  2. If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.missing from 1 of 4
  3. Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."missing from 1 of 4
  4. Should any tickets be merged or split further?missing from 1 of 4

Rules people drop

  1. Do NOT close or modify any parent issue.dropped by 11 of 32
  2. Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."dropped by 7 of 32
  3. If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.dropped by 6 of 32
  4. Should any tickets be merged or split further?dropped by 4 of 32

Rules people add

  1. No tracker configured (no MCP server, or the IDs are blank): publish local files under docs/plans/<feature-slug>/ instead (step 5). docs/plans/ is local-only; scripts/pre-commit refuses to commit it.added by 2 of 32
  2. Local files: write one file per ticket under .scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered in dependency order (blockers first).added by 2 of 32

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Rising: 10 new projects took it in the last 4 weeks, 1.4× the 4 weeks before.

Week of Sep 20: 1 new projectWeek of Sep 27: 3 new projectsWeek of Oct 4: 1 new projectWeek of Oct 11: 2 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 4 new projectsWeek of Nov 1: 4 new projectsWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use to-specs.

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.
  • sponge-b0bSkill

    to-specs

    Project decision-complete planning into implementation Specs from exact Canonical Contract Ledger semantics while preserving Independent Specs and existing Spec identity.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 4 are common, 0 are distinctive, and 0 are very specific to this project.

  • 4

    Common

    Most of the 157 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 157 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.