track
Backlog CRUD through the bound tracker: stats, list, add, start, done, due, recheck, search, audit, publish-plan, link (default: stats). Use when the user wants to add, claim, or close a work item, ticket, or issue; list, search, or see a dashboard of open items; check what is due on the recurring schedule; or audit stale claims and labels. New bug reports go to /bugs:write first. Picking and executing the next item is /work-items:work; raw intake is /work-items:triage.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- metadata
- { "summary": "Backlog CRUD through the bound tracker. Add, list, close, stats", "workflow-stage": "anytime" }
- description
- Backlog CRUD through the bound tracker: stats, list, add, start, done, due, recheck, search, audit, publish-plan, link (default: stats). Use when the user wants to add, claim, or close a work item, ticket, or issue; list, search, or see a dashboard of open items; check what is due on the recurring schedule; or audit stale claims and labels. New bug reports go to /bugs:write first. Picking and executing the next item is /work-items:work; raw intake is /work-items:triage.
- argument-hint
- [stats|list|add|start|done|due|recheck|search|audit|publish-plan|link|view|edit|changes…] [args]
- user-invocable
- true
- disable-model-invocation
- false
02 资源文件 15
- 参考文档actions/add.md16.6 KB
- 参考文档actions/audit.md5.9 KB
- 参考文档actions/changes.md1.3 KB
- 参考文档actions/done.md6.8 KB
- 参考文档actions/due.md3.9 KB
- 参考文档actions/edit.md2.8 KB
- 参考文档actions/labels.md802 B
- 参考文档actions/link.md2.6 KB
- 参考文档actions/list.md2.2 KB
- 参考文档actions/publish-plan.md3.9 KB
- 参考文档actions/recheck.md4.0 KB
- 参考文档actions/search.md1.9 KB
- 参考文档actions/start.md10.8 KB
- 参考文档actions/stats.md1.7 KB
- 参考文档actions/view.md3.3 KB
03 SKILL.md 正文
Variables
Arguments: $ARGUMENTS. [stats|list|add|start|done|due|recheck|search|audit|publish-plan|link|view|edit|changes|labels|help] [args]. The default action is stats.
Shared tracker context
The seam, operation routing, label taxonomy, canonical-role remapping, recurring schedule, and
memory-tier write rule 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 bind the
actions below:
- 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, andauditquery, create, or filter items by a canonical role. Resolve each role fromconfig.role_labelsof the binding the seam resolves (thetrackermapping of<home>/work-items.yaml) 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 read:
${CLAUDE_PLUGIN_ROOT}/reference/label-taxonomy.md: the label structureaddvalidates against andlist --categoryfilters by.${CLAUDE_PLUGIN_ROOT}/reference/issue-conventions.md: the item shapeaddfollows; its title rule points at the house style.${CLAUDE_PLUGIN_ROOT}/reference/agent-brief.md: the brief templateadd --agent-readyuses instead of the default body.${CLAUDE_PLUGIN_ROOT}/reference/standing-item-preconditions.md: the preconditionrecheckevaluates before advancing dates or closing the associated item.
Scope
track is the concurrent-safe backlog-CRUD surface, routed by the action table below. Selecting
and executing one item, raw-intake evaluation, plan decomposition and the marker sweep belong to
the sibling skills under "Sibling-skill verbs".
Emit checklist
For the multi-step actions (add, start, done, recheck), 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
(${CLAUDE_PLUGIN_ROOT}/reference/tracker-seam.md
"Memory-tier writes" owns the slug and the self-ignore guard).
Tick each step as completed. Single-action reads (stats, list, search, due, view, changes,
labels), audit and edit don't need a checklist.
Next
- A picked item:
/work-items:work. - Raw intake:
/work-items:triage.
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 |
list |
List work items with label/state/assignee filtering | actions/list.md |
add |
Create a new work item with labels from the taxonomy | actions/add.md |
start |
Claim an item (assignee + lease via the seam) | actions/start.md |
done |
Close an item with a completion comment | actions/done.md |
due |
Show recurring items past their next_due date |
actions/due.md |
recheck |
Update last_checked/next_due in recurring schedule after a periodic check |
actions/recheck.md |
search |
Full-text search across items (open + closed) | actions/search.md |
audit |
Detect stale claims, orphaned recurring entries, label hygiene; close decomposed parents whose children are done | actions/audit.md |
publish-plan |
Post an approved PLAN.md to an item as one marked comment, edited in place on re-publish | actions/publish-plan.md |
link |
The adapter's text linking a change to an item, from an id or a branch name | actions/link.md |
view |
One item's title, state, labels and body, and its comments with --comments |
actions/view.md |
edit |
Change an item's title, body or labels, add a blocked-by edge, or comment | actions/edit.md |
changes |
Change requests the tracker links as closing an item | actions/changes.md |
labels |
The live label set, or which named labels are missing | actions/labels.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.
Sibling-skill verbs. work, triage, decompose, and scan are standalone skills, not
track sub-actions. If $ARGUMENTS names one, 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.
04 同仓库更多 Skills
work
Pick exactly one work item from the tracker frontier by priority tier (due recurring, guardrails, highest impact, then not-yet-due recurring), claim it race-safe, and execute it end-to-end through the project's workflow. Use when the user asks to pick, grab, or work the next item, ticket, or issue, or asks what to work on next. Backlog CRUD is /work-items:track; draining the backlog in a loop is /work-items:work-loop.
work-loop
Drain the work-item backlog as a self-paced autonomous loop, launched via /loop: each cycle triages raw intake, admits items through the fail-closed admission gate, runs them through /work-items:work under an adaptive cap, and checks the drain exit. Authors PRs, never merges. Use when: 'work loop', 'run the work loop', 'start the worker loop', 'drain the backlog', 'autonomous drain', 'loop the backlog', 'drain the issue backlog to done'. Escalations: /work-items:attend-queue.
triage
Evaluate raw intake, any untriaged item whoever filed it (bug reports, feature requests, unsolicited PRs, dogfood issues): raw, verified, briefed, autonomous-eligible, with exits to needs-info, human-gated, close. Use when: 'triage', 'what needs triage', 'triage this issue', 'triage this PR', 'evaluate this bug report', 'is this bug real', 'should we merge this unsolicited PR', 'attention view', 'what intake needs attention', 'sweep needs-human'. No number: the attention view. Escalations: /work-items:attend-queue.
ship
Route and run one spec container's multi-session effort: where it stands, which execution shape is in effect (per-item PRs or one integration branch) and its discipline, the next step; `run` works its ready items in parallel, landing one at a time. Use when the user says 'ship' about a spec or container, asks where it stands or what is next, wants to run, drive or resume it, or close it out. One item: /work-items:work; re-slicing: /work-items:decompose.
setup
Verify and configure the work-items plugin for this repo. check read-only inspects the tracker binding (the home's work-items.yaml), tracked .github/recurring-schedule.json (presence, JSON validity, unique reconciliation keys), jq and tracker-seam entry gates, recurring-maintenance role label, provenance and capability-tier labels; apply binds the provider (copying legacy JSON), writes the schedule, migrates provenance and capability-tier labels when authorized, backfills legacy frontier stamps, and optionally remaps role labels. First-time bind writes minimum viable config only; per-item schedule seeding is opt-in via --seed-schedule. Use when: 'set up work-items', 'bind the tracker provider', 'is work-items configured', 'configure the recurring schedule', 'work-items setup', 'seed recurring items', 'bulk-seed the recurring schedule', 'remap the work-item role labels', or the due/recheck/work actions report no recurring schedule configured, or the seam reports no binding. Re-runnable.
scan-todos
Sweep source comments, not tracker items, for TODO/FIXME/HACK/XXX markers and resolve or file each one. Use when: 'scan TODOs', 'scan for FIXME', 'sweep the codebase for markers', 'find TODO comments', 'resolve TODO/FIXME/HACK', 'scan for tech-debt comments', 'clean up markers'. Not the workflow for new work: durable work belongs in the tracker when it is written. Tracker items go to /work-items:track.