Track development work items through the bound tracker (work-item-tracker seam), the backlog-CRUD multi-verb skill. Actions: stats, list, add, start, done, due, recheck, search, audit (default: stats dashboard). Use when: 'add a work item', 'add an issue', 'add a ticket', 'close a work item', 'close a ticket', 'close an issue', 'start a work item', 'start a ticket', 'start an issue', 'claim a work item', 'list work items', 'list tickets', 'list issues', 'what work items are open', 'what's due...
Scanned 9/2/2026
Install to Claude Code
npx -y skills add melodic-software/claude-code-plugins --skill track --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Track?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/melodic-software-track)More formats (shields.io, HTML) on the badges page.
---
description: "Track development work items through the bound tracker (work-item-tracker seam), the backlog-CRUD multi-verb skill. Actions: stats, list, add, start, done, due, recheck, search, audit (default: stats dashboard). Use when: 'add a work item', 'add an issue', 'add a ticket', 'close a work item', 'close a ticket', 'close an issue', 'start a work item', 'start a ticket', 'start an issue', 'claim a work item', 'list work items', 'list tickets', 'list issues', 'what work items are open', 'what's due', 'work-item stats', 'work items dashboard', 'search work items', 'check overdue recurring items', 'recheck a recurring item', 'audit work items', 'audit stale claims'. Not for new bug reports, use /bugs:write first (read-only report), then chain to /work-items:track add via --context if filing is needed. Sibling skills own the other verbs: /work-items:work (auto-select + execute one), /work-items:triage (raw intake), /work-items:decompose (plan → tickets), /work-items:scan-todos (TODO/FIXME sweep)."
argument-hint: "<action> [args]. Actions: stats, list, add, start, done, due, recheck, search, audit (default: stats)"
user-invocable: true
disable-model-invocation: false
metadata:
workflow-stage: anytime
summary: Backlog CRUD through the bound tracker. Add, list, close, stats
---
## Variables
Arguments: `$ARGUMENTS`
## Shared tracker context
The seam, operation routing, label taxonomy, canonical-role remapping, recurring schedule, and
topic-docs binding that every work-items skill relies on live in
[`${CLAUDE_PLUGIN_ROOT}/reference/tracker-seam.md`](${CLAUDE_PLUGIN_ROOT}/reference/tracker-seam.md)
(and the references it links). Read it at the start of an invocation. Two invariants bear on the
actions below in particular:
- **Provider-neutral over the seam.** Coordination goes through
`${CLAUDE_PLUGIN_ROOT}/tools/work-item-tracker/work-item-tracker.sh <verb>`; provider mechanics (filtered listing,
search, aggregation, close, label/comment edits) route through the bound adapter's operations
reference. The core inlines no provider commands.
- **Role-label resolution is an action-entry invariant.** `add`, `due`, `recheck`, and `audit`
query, create, or filter items by a canonical role. Resolve each role from
`.work-item-tracker.json` `config.role_labels` at action entry and use the resolved strings in
every query. When a role defaults because the file or entry is absent, warn loudly rather than
substituting silently; a present malformed/empty/non-string value is a hard stop.
`add` and `recheck` also draw on reference files the seam doc above does not itself carry:
- [`${CLAUDE_PLUGIN_ROOT}/reference/label-taxonomy.md`](${CLAUDE_PLUGIN_ROOT}/reference/label-taxonomy.md):
the 8-group label structure `add` validates against and `list --category` filters by.
- [`${CLAUDE_PLUGIN_ROOT}/reference/issue-conventions.md`](${CLAUDE_PLUGIN_ROOT}/reference/issue-conventions.md):
the title convention `add` applies.
- [`${CLAUDE_PLUGIN_ROOT}/reference/agent-brief.md`](${CLAUDE_PLUGIN_ROOT}/reference/agent-brief.md):
the brief template `add --agent-ready` uses instead of the default body.
- [`${CLAUDE_PLUGIN_ROOT}/reference/standing-item-preconditions.md`](${CLAUDE_PLUGIN_ROOT}/reference/standing-item-preconditions.md):
the precondition `recheck` evaluates before advancing dates or closing the associated item.
## Scope
`track` is the centralized, concurrent-safe backlog-CRUD surface: create, claim, close, list,
search, dashboard, and the recurring-schedule checks. It keeps a sub-action router over nine verbs.
Auto-selecting and executing one item is the sibling `/work-items:work` skill; raw-intake
evaluation is `/work-items:triage`; plan decomposition is `/work-items:decompose`; the codebase
marker sweep is `/work-items:scan-todos`.
## Emit checklist
For the multi-step actions (`add`, `start`, `done`, `recheck`), instruct the agent to copy the
matching action section of
[`${CLAUDE_PLUGIN_ROOT}/templates/checklist.md`](${CLAUDE_PLUGIN_ROOT}/templates/checklist.md) into
`<memory_dir>/<slug>/work-items-checklist.md` (default `.work/`), a memory-tier write under this
plugin's topic-docs binding
([`${CLAUDE_PLUGIN_ROOT}/reference/topic-docs.md`](${CLAUDE_PLUGIN_ROOT}/reference/topic-docs.md)):
derive `<slug>` per its slug spec and, on the session's first memory-tier write, verify the resolved
memory root's self-ignore guard (a `.gitignore` containing `*`, created and announced when absent).
Tick each step as completed. Single-action reads (`stats`, `list`, `search`, `audit`, `due`) don't
need a checklist.
## Action Router
Parse `$ARGUMENTS` to extract the action (first token) and remaining arguments.
| Action | Description | Detail |
|--------|-------------|--------|
| `stats` | Dashboard: open/claimed counts, overdue recurring, category breakdown | [actions/stats.md](actions/stats.md) |
| `list` | List work items with label/state/assignee filtering | [actions/list.md](actions/list.md) |
| `add` | Create a new work item with labels from the taxonomy | [actions/add.md](actions/add.md) |
| `start` | Claim an item (assignee + lease via the seam) | [actions/start.md](actions/start.md) |
| `done` | Close an item with a completion comment | [actions/done.md](actions/done.md) |
| `due` | Show recurring items past their `next_due` date | [actions/due.md](actions/due.md) |
| `recheck` | Update `last_checked`/`next_due` in recurring schedule after a periodic check | [actions/recheck.md](actions/recheck.md) |
| `search` | Full-text search across items (open + closed) | [actions/search.md](actions/search.md) |
| `audit` | Detect stale claims, orphaned recurring entries, label hygiene | [actions/audit.md](actions/audit.md) |
| `help` | Show the action table above | *(inline)* |
If `$ARGUMENTS` is empty, run `stats` (the default dashboard). If the action is unknown, show the
action table.
**Verbs that moved to sibling skills.** `work`, `triage`, `decompose`, and `scan` are no longer
`track` sub-actions. They are standalone skills. If `$ARGUMENTS` names one of them, point the user
at the skill instead of erroring: `work` → `/work-items:work`, `triage` → `/work-items:triage`,
`decompose` → `/work-items:decompose`, `scan` → `/work-items:scan-todos`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!