Set up the issue tracker

Give this repository one issue tracker convention that the other skills read through a short route in its agent instructions. The spec folder under docs/specs/<slug>/ stays the implementation contract. A spec-first folder gets a derived pointer issue after merge; when triage starts from an existing human-written issue, that original issue stays the only issue for the work. Repositories without this section keep every skill's current behavior. Write it when the user wants parallel implementation or scheduled general-issue triage.

Explore, then recommend

Read what is already there before asking anything: the Git remotes, whether AGENTS.md and CLAUDE.md exist and whether either already carries an issue tracker section, and which tracker tools this session can actually use (a GitHub CLI login, a Linear MCP server or CLI, or nothing). Lead with a recommendation the user can accept in a word: the remote's host when the repository lives on GitHub, an existing section's tracker when one exists, and otherwise the tool the session can reach. Confirm one item at a time.