agentleFS
Sign inStart free
kyoo-147kyoo-147/MinimalShip/skills/engineering/to-tickets/SKILL.md

to-tickets

Skill0 starsChanged 25 days agoMITView on GitHub

Break a product spec into small tracer-bullet work items with explicit dependency edges and acceptance checks.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, claude-handoff and 6 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.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 40 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 47 projects that use this

  • 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

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 43 projects that use this

  • LesaniSkill

    writing-fragments

    Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.

    Also in 43 projects that use this

  • +1 more from Lesani

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 183 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
  1. Distinctive:

    Start from the acceptance cases, not a list of imagined technical tasks.

    line 9
  2. Distinctive:

    Create a runnable skeleton first when the system is new.

    line 10
  3. Distinctive:

    Keep a single owner for shared interfaces and manifests.

    line 14
  4. Distinctive:

    Prefer a local Markdown table when no issue tracker is configured.

    line 15
  5. Very specific:

    Keep the resulting task IDs and ownership in RUN.md.

    line 19

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

To Tickets

  • Start from the acceptance cases, not a list of imagined technical tasks.
  • Create a runnable skeleton first when the system is new.
  • Give each ticket one vertical result and one acceptance check.
  • Mark blocking edges explicitly: contract, schema, environment, or prior slice.
  • Assign a path or worktree boundary so parallel workers cannot edit the same mutable file.
  • Keep a single owner for shared interfaces and manifests.
  • Prefer a local Markdown table when no issue tracker is configured.

A ticket is ready only when an implementer can start without asking what "done" means.

Keep the resulting task IDs and ownership in RUN.md; update the corresponding rows in FEATURES.md only when a feature status changes. Do not create a second task tracker.

Download now (ZIP)

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.

Check your setup, free