task-tracker
Skill6 starsChanged 24 days agoNo licenceView on GitHub
How work is created and tracked in your team's task tracker (Jira, GitHub Projects, Asana, Linear or any other) — the tracker-neutral model (one active project, the hierarchy Epic → Story/Task/Bug/Investigation → Subtask, an Epic is a goal and not a folder, Epic naming and the domain tag, sprints, the ticket states and their transitions — Refining, Refined, Validating, Discard —, the ticket fields for criteria, artifacts and design, blocking links, how to discard a ticket even when something is already installed) and how each concept maps to each tool, with one reference per tool. Use when creating or reorganizing tickets, deciding whether something is an Epic, reading or moving a ticket, or when someone asks "what states does the board have" or "which state do I move this to". Invoke as /task-tracker.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- shubhomoydas/claude_skillstheir own version, first seen Nov 1, 2026
- rcelebrone/DotAgentstheir own version, first seen Oct 14, 2026
- bkywksj/knowledge-basetheir own version, first seen Oct 8, 2026
- nuffin/hermes-task-frameworktheir own version, first seen Sep 28, 2026
- claude-world/claude-agenttheir own version, first seen Mar 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- bkywksj/knowledge-base★ 340same name
- rcelebrone/DotAgents★ 15same name
- claude-world/claude-agent★ 5same name
- nuffin/hermes-task-framework★ 2same name
- shubhomoydas/claude_skills★ 0same name
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 repository18 other files it gives its agents.
- acceptance-criteriaSkill
- app-designSkill
- ci-cdSkill
- credentialsSkill
- definition-of-readySkill
- feature-flagsSkill
- gate-policiesSkill
- gitflowSkill
- grafana-dashboardsSkill
- kubectlSkill
- observabilitySkill
- pull-requestSkill
- refinement-contextSkill
- rollout-planSkill
- secret-or-settingSkill
- skill-designSkill
- test-appsSkill
- ticket-lifecycleSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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 an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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.