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.
• Dependencies: docs/dev-agents/config.md with issue_tracker set, written by setup. For GitHub, an authenticated gh against a host with native issue dependencies. For Linear, the Linear MCP server. For local, nothing.
• How to call it: Claude Code /tracker <verb> [args], Codex $tracker <verb> [args], Kiro CLI /tracker <verb> [args].
• Input: one verb and its arguments.
• Output: the tickets asked for, or the changed ticket state plus its URL or file path.

1. Resolve the backend

Read issue_tracker from docs/dev-agents/config.md, then read exactly one backend file, all the way through, before running anything: