Setup Tracer

Scaffold the per-repo configuration the tracer skills read:

• Issue tracker — where /tracer-wayfinder charts decision maps, /tracer-to-spec and /tracer-to-tickets publish, and /tracer-code-review fetches specs from (GitHub, GitLab, local markdown, or a workflow you describe)
• Domain docs — where CONTEXT.md and ADRs live, and the consumer rules for reading them

Skipping setup is fine: every skill falls back to local markdown under .tracer/. Run this when you want a real tracker, or to make the conventions explicit for other agents working in the repo.

This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.

Process

1. Explore

Read whatever exists; don't assume: