The workflow describes a change in the traceability graph, but backlog, assignment, priority, and reporting live in an issue tracker such as Jira or GitHub. Today the only glue is a human pasting a tracker URL into a change’s prose, so the spec graph and the board drift apart. Projects need a stable pointer between a change and its tracker issue, a configurable declaration of where that tracker lives, and thin skills to move issues at lifecycle boundaries.

A tracer-spec-owned configuration file tspec.yml declares an optional tracker (provider none by default, plus github and jira, with reachability and an optional status map). A trackerId attribute on the change item block header is the stable pointer to the tracker issue, with no change to the traceability grammar. One tspec-track skill links or creates an issue when a change is proposed, imports a tracker-first issue as a seeded change, and pushes status at accepted, implemented, and closed transitions — always one-way, never reconciling tracker state back into the graph.

Bidirectional synchronization. Webhooks. Comment mirroring. Any provider beyond GitHub and Jira.