implement-ticket
Skill0 starsChanged 46 days agoNo licenceView on GitHub
Implement one issue or ticket end to end in the current repository. Use when the user asks the current agent to tackle, fix, or deliver one ticket, even when the request also names a worktree, pull request, adversarial review, or CI. The current agent writes the code and uses one subagent only for review. The user remains the orchestrator. Do not delegate implementation or invoke orchestrate-implementation. Requests to dispatch implementation or coordinate multiple tickets in parallel route to orchestrate-implementation instead.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- fboulnois/skillstheir own version, first seen Nov 8, 2026
- islandhopper81/claude-skillstheir own version, first seen Nov 1, 2026
- K-log/skillstheir own version, first seen Nov 1, 2026
- crissmoldovan/agent-skillstheir own version, first seen Nov 1, 2026
- hoangliem88/claude-skillstheir own version, first seen Oct 13, 2026
- nhhthong/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use thermo-nuclear-code-quality-review, implement-spec and 8 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.
jaydubya818Skillthermo-nuclear-code-quality-review
Use when the user requests an intentionally strict maintainability review.
Also in 3 projects that use this
AWSSkillimplement-spec
Implement the result of /to-spec and /to-tickets in code.
Also in 3 projects that use this
GoogleSkillto-tickets
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.
Also in 3 projects that use this
- GoogleSkill
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
- +4 more from google
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- blockscout/frontend★ 310same name
- sponge-b0b/Polaris★ 4same name
- crissmoldovan/agent-skills★ 2same name
- Pawel-Kica/ai-coding-100★ 2same name
- Pawel-Kica/claude-code-100★ 2same name
- anarefin/ai-agent-skills★ 1same name
- fboulnois/skills★ 1same name
- nhhthong/skills★ 1same name
- oleg-chibikov/agent-skills★ 1same name
8 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 repository8 other files it gives its agents.
- adopt-orchestrationSkill
- design-agent-workflowSkill
- execute-runbookSkill
- open-pull-requestSkill
- orchestrate-implementationSkill
- orientationSkill
- resume-orchestrationSkill
- run-decision-queueSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
40 rules. 0 are common, 37 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
37
Distinctive
This author's own choices. Worth a look.
3
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 17 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
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.