Configure Issue Tracker

Sets up or updates issue tracking for a repo. Writes config to docs/agents/ and wires progressive disclosure into CLAUDE.md and AGENTS.md. For GitHub backends, also provisions labels, Project fields, and org-level Issue Types via the gh CLI. Does not create or manage individual issues.

Modes

Check first: does docs/agents/issue-tracker.md exist?

• No → Init: run the full interview, then write all output files and provision GitHub (if applicable).
• Yes → Update: load existing config, show a summary, ask which sections the user wants to change, re-interview only those sections.

Workflow

1. Check for existing config — read docs/agents/issue-tracker.md if it exists.
2. Run the interview — see INTERVIEW.md for the entry point and routing to backend-specific and shared interview files. Present defaults visibly; only drill into sub-questions when the user wants to override.
3. Review & approve — present a full summary of all decisions and all actions that will be taken (files to write, GitHub API calls to make). Wait for explicit approval before proceeding.
4. Write output files and provision — see OUTPUTS.md for formats and templates.
5. Confirm — show the user a summary of what was written and what was provisioned.