to-tickets
Skill4 starsChanged 4 months agoApache-2.0View on GitHub
Decompose one deterministic Spec contract or structured Spec Review remediation contract into executable tickets with human-approved slicing and exact machine coverage.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- moisesrj97/skillstheir own version, first seen Nov 16, 2026
- endalk200/skillstheir own version, first seen Nov 16, 2026
- atiq-r/skillstheir own version, first seen Nov 16, 2026
- devdeepjs/kobayashi-marutheir own version, first seen Nov 16, 2026
- zademy/lu-querytheir own version, first seen Nov 16, 2026
Used with
Projects with it also use setup-ts-deep-modules, to-questionnaire and 9 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.
liufeng1976Skillsetup-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 49 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 102 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 54 projects that use this
richard12511Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 46 projects that use this
AWSSkillimplement-spec
Implement the result of /to-spec and /to-tickets in code.
Also in 86 projects that use this
LesaniSkillwriting-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 51 projects that use this
- +2 more from aws
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- mattpocock/skills★ 325ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame name
- bestofjs/bestofjs★ 3.1ksame name
- bamlab/flashlight★ 1.6ksame name
- moeru-ai/xsai★ 669same name
182 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 repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-remediationSkill
- attentionSkill
- classify-docSkill
- codebase-designSkill
- codebase-memory-mcpSkill
- codegraphSkill
- coding-standardsSkill
- contract-ledgerSkill
- conventional-commitsSkill
- database-migrationsSkill
- deduplicate-codeSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- format-codeSkill
- github-issue-dependenciesSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implement-ticketSkill
- improve-codebase-architectureSkill
- project-delivery-managementSkill
- project-trackingSkill
- prototypeSkill
- repowiseSkill
- researchSkill
- resolving-merge-conflictsSkill
- review-architectureSkill
- review-specSkill
- setup-matt-pocock-skillsSkill
- spec-contractSkill
- spec-merge-cleanupSkill
- tddSkill
- teachSkill
- to-adr-docSkill
- to-docSkill
- to-specsSkill
- triageSkill
- verify-architectureSkill
- verify-codeSkill
- verify-spec-closureSkill
- verify-specSkill
- verify-ticket-closureSkill
- verify-ticket-decompositionSkill
- wayfinderSkill
- wiki-lintSkill
- wiki-syncSkill
- wiki-synthesizeSkill
- writing-great-skillsSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
7
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
- Distinctive: line 12
Before executing this skill, read all of these files in full:
- Distinctive: line 28
All retained requirements remain mandatory unless explicitly overridden here.
- Distinctive: line 39
Before approval, the retained Attention consumer remains mandatory:
- Distinctive: line 50
Before changing ownership or dependencies of an already-started ticket, do not merely note that recovery may be needed later.
- Distinctive: line 58
leave the protected donor checkout byte-for-byte unchanged.
- Distinctive: line 64
read that record back exactly.
- Distinctive: line 86
When live-WIP recovery applies, the Pre-publication workflow receipts must include the five exact current-run recovery receipt lines …
- Very specific: line 97
Do not stop after the first actionable ticket: Create one handoff entry for every actionable ticket in ordinary destination/topology order …
“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.
Files
To Tickets
Authoritative procedure composition
Before executing this skill, read all of these files in full:
.agents/skills/to-tickets/PROCEDURE.md.agents/skills/to-tickets/CONTROL_PLANE.md.agents/skills/to-tickets/TICKET_RESLICE_RECOVERY.md
Compatibility form retained for policy validation: read .agents/skills/to-tickets/PROCEDURE.md in full.
CONTROL_PLANE.md preserves the previously authoritative $to-tickets entrypoint,
including architecture-blocker finalization, human approval, publication/readback, and the
complete actionable frontier / shared Human Handoff contract. PROCEDURE.md preserves the
deterministic ticketing lifecycle. TICKET_RESLICE_RECOVERY.md is the canonical durable
contract for live-WIP reslicing and overrides any shorter or older recovery summary in the
retained files. On any other conflict, this file wins; on conflict, this file wins. Failure to
load any required file is a Hard Blocker.
All retained requirements remain mandatory unless explicitly overridden here.
9A. Routed architecture-blocker finalization
The retained Section 9A remains authoritative. A deterministic routed -> resolved
transition must PATCH that same managed comment in place and must finish with:
Unresolved/routed blockers remaining on design-ready tickets: 0Before approval, the retained Attention consumer remains mandatory:
python -m scripts.workflow_attention validate \
--result <attention-result-file> \
--checkpoint '$to-tickets pre-publication' \
--require-nonblockingLive-WIP reslice durability boundary
Before changing ownership or dependencies of an already-started ticket, do not merely note
that recovery may be needed later. Complete the publication-time capture in
TICKET_RESLICE_RECOVERY.md before human approval and before ticket/coverage/routing
mutation whenever the proposed reslice can overlap, provide, supersede, move, or precede
active WIP.
The capture must:
- leave the protected donor checkout byte-for-byte unchanged;
- preserve an already-pinned Source ticket baseline exactly;
- attribute every dirty tracked hunk and untracked path exactly once;
- determine
source-firstversusdestination-firstfrom the proposed native dependency graph; - persist exactly one
ticket-reslice-recovery:v1managed record on the Destination ticket; - read that record back exactly; and
- validate the readback mechanically:
python -m scripts.workflow_reslice_recovery validate \
--body <recovery-comment-body-file>Require:
TICKET RESLICE RECOVERY: VALIDA nonzero validator result, ambiguous donor ownership, uncertain execution order, donor fingerprint drift, or missing recovery metadata blocks approval/publication.
For new recovery records include the explicit Execution order and Destination baseline
fields defined by the shared contract. Existing v1 records may use only the documented
machine-derivable compatibility path and must gain explicit fields at their next authorized
update.
When live-WIP recovery applies, the Pre-publication workflow receipts must include the five exact current-run recovery receipt lines required by the shared contract in addition to the retained Project Delivery, Spec contract, decomposition, architecture-blocker, and Attention receipts.
Human approval authorizes only the exact proposal that includes this recovery state. It does not authorize mutation of the protected donor checkout.
Retained Human Handoff contract
The retained frontier rule is unchanged: evaluate the complete actionable frontier and
Do not stop after the first actionable ticket. Create one handoff entry for every actionable ticket
in ordinary destination/topology order or review-remediation proposal alias order as
applicable. Every destination is $implement-ticket.
Finalize terminal handoffs only through the shared runtime resolver:
python .agents/skills/shared_handoff_runtime.py finalize \
--manifest <handoff-manifest.json> \
--output <handoff-output.txt> \
--repo-root .The resolver may use candidate-local scripts.workflow_handoff only when it satisfies the
current versioned shared runtime contract. Otherwise it fetches current origin/main,
materializes only the canonical shared handoff runtime closure in a temporary location, and
generates/verifies there without mutating the candidate branch.
Require WORKFLOW HANDOFF: VALID. The user-visible handoff reproduces the generated output
byte-for-byte. Do not emit a bare $implement-ticket line and do not hand off a
participant whose native blockers or recovery state make it non-actionable.
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.

