Configure Issue Tracker

Configure Issue Tracker

Record the repository's issue and intent backend in docs/agents/issue-tracker.md. Optionally connect that configuration to an existing AGENTS.md without taking ownership of the rest of the file.

This skill configures local files only. It does not create remote repositories, issues, or labels, and it does not create or replace AGENTS.md or CLAUDE.md.

Inspect first

1. Read an existing docs/agents/issue-tracker.md in full.
2. Read root-level AGENTS.md if present and check whether it already points to the tracker configuration or describes the intent-to-PR workflow.
3. Run git remote -v. Normalize ordinary GitHub HTTPS and SSH URLs to owner/repo, stripping a trailing .git. If fetch and push URLs disagree, multiple remotes are plausible, or the remote may be a fork, present the candidates rather than choosing one. Every inferred location is a proposal, not confirmation of the user's intended tracker.
4. Check git status, then summarize the current state before changing it.

Confirm the backend

Ask where issues and intents should live:

Do not inspect, create, or update remote labels as part of configuration. A later issue-creation workflow may do so with the required authorization.

Write the configuration

Create docs/agents/ if needed, preserving every file already there. Write docs/agents/issue-tracker.md with this shape:

# Issue tracker

<!-- Read by: brainstorm-to-issue, and any future spec/plan/triage skills -->

## Backend
<GitHub, Local markdown, or the named backend>

## Location
<confirmed owner/repo, local path, or tracker location>

## Labels
<confirmed labels, or None>

## Notes
<user-provided details, or None>

For GitHub, record the intent label as - <label> — applied to issues created by brainstorm-to-issue. For an existing configuration, show the proposed differences and obtain confirmation before replacing real values. Re-running with the same values is a no-op.

Connect an existing AGENTS.md

If root-level AGENTS.md does not exist, leave it absent. The tracker configuration is still usable; recommend agent-md-setup if the user wants shared repository instructions.

If AGENTS.md exists, read assets/AGENTS-sections.md and show the user the exact missing entries or sections. Tracker selection does not implicitly approve this optional edit: show its patch and obtain confirmation, which may be combined with the backend confirmation in one question.

• Merge the tracker entry into an existing Agent configuration section when one exists; do not duplicate the heading.
• Preserve an existing Workflow section. If it lacks the intent-to-PR steps, show a surgical merge of the missing steps. If existing steps conflict with the supplied workflow, show the conflict and ask which text should remain.
• Do not reorder, rewrite, or reformat unrelated project instructions.

Finish

Read back the tracker configuration and inspect the final diff. If AGENTS.md changed, confirm that only the approved entry or sections changed. Report the backend, location, label configuration, and any file deliberately left untouched. A completed tracker file remains valid when the optional AGENTS.md integration is declined or deferred; report that state plainly. Stop without creating an issue or invoking another skill.

What NOT to do

• Don't guess the tracker, GitHub repository, local path, or label.
• Don't mutate GitHub or another remote service during local configuration.
• Don't overwrite a populated tracker configuration without showing the differences and receiving confirmation.
• Don't create AGENTS.md or CLAUDE.md; that belongs to agent-md-setup.
• Don't replace an existing AGENTS.md with a template or rewrite unrelated guidance.
• Don't create intent issues, specs, plans, or pull requests as part of setup.