wkc-tracker

• What it does: reads and writes ticket state against the backend named by issue_tracker in docs/dev-agents/config.md: GitHub Issues, Linear, or local markdown files.
• When to use it: any time a skill or a person needs to see or change ticket state. Every other skill in this set goes through these verbs instead of touching the backend directly. Callers are people, models, and any wkc- skill that needs ticket state. A model may read on its own, but runs a verb that changes state only when a person or a calling skill asked for that change.
• Dependencies: docs/dev-agents/config.md with issue_tracker set, written by wkc-setup. For GitHub, an authenticated gh against a host with native issue dependencies. For Linear, the Linear MCP server. For local, nothing.
• Input: one verb and its arguments, as documented in section 4, plus the configured backend. The verb table explains ticket ids, text, statuses, milestones, holders, and dependency edges. Optional arguments keep their existing behaviour: list without filters returns open tickets; bare assign <id> takes the ticket. next needs no arguments.
• Output: the tickets asked for, or the changed ticket state plus its URL or file path.

1. Resolve the backend