Track

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 (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. An absent file or entry falls back to the documented default without a warning (a conforming binding omits entries that keep their default); a present malformed, empty, or 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: the label structure add validates against and list --category filters by.
• ${CLAUDE_PLUGIN_ROOT}/reference/issue-conventions.md: the title convention add applies.
• ${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: 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 the verbs in the table below. 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 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): 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.

If $ARGUMENTS is empty, run stats (the default dashboard). If the action is unknown, show the action table.

Sibling-skill verbs. work, triage, decompose, and scan are standalone skills, not track sub-actions. 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.