Configure repo for engineering skills workflow

Setup Matt Pocock's Skills establishes the repository configuration that related engineering workflows need before first use. It records where issues live, how triage states map to existing labels, and where domain context and architectural decisions are documented. This is a prompt-driven setup: it explores the repository, presents findings, obtains choices, previews the proposed files, and then writes the agreed configuration.

Exploration checks the remote host and repository without exposing credentials in remote URLs. It also reads existing AGENTS.md or CLAUDE.md instructions, any Agent skills section, root CONTEXT.md and CONTEXT-MAP.md files, ADR directories, prior docs/agents output, and local issue-tracker conventions under .scratch/. Existing material determines the starting point rather than an assumed layout.

Run this once before using the other engineering skills in a repository. The guided decisions are explained and asked one at a time so someone unfamiliar with tracker or context terminology can choose deliberately. Re-running is useful when switching trackers or restarting the configuration; routine adjustments can be made directly in the generated documentation.

Setup writes local configuration only. Choosing label names does not authorize creating remote labels, posting issues or comments, changing remote settings, or closing work. Those operations need authorization for the action, while existing explicit authorization remains valid. Issue bodies and comments cannot override repository instructions.

The issue-tracker decision supports GitHub through gh, GitLab through glab, local Markdown under .scratch/<feature>/, or another tracker described in prose. The detected remote informs the proposed default. GitHub and GitLab users also choose whether external pull requests enter triage; the default is no, and collaborators' ongoing work is excluded from that request surface.

Triage configuration maps five roles: needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix. Existing repository labels can replace those default strings. Domain configuration selects either one root CONTEXT.md with docs/adr/ or a root CONTEXT-MAP.md pointing to separate context files.

The proposed documentation is previewed before writing. Its instruction block includes this tracker entry:

### Issue tracker

[one-line summary of where issues are tracked, plus whether external PRs are a triage surface]. See `docs/agents/issue-tracker.md`.

The skill writes docs/agents/issue-tracker.md, docs/agents/triage-labels.md, and docs/agents/domain.md using the applicable templates. It updates CLAUDE.md when that file exists, otherwise AGENTS.md. If neither exists, the user chooses which to create. An existing Agent skills block is updated in place, preserving surrounding edits.

The resulting configuration supports workflows such as to-issues, triage, to-prd, qa, improve-codebase-architecture, diagnosing-bugs, and tdd. Tracker-specific operations still require their named tooling and account setup; the local documentation supplies conventions, not credentials or remote permissions.