setup-agent-routinglisted

# Setup Agent Routing Write a machine-readable routing block so the dev-loop skills know where this repo tracks work, which labels drive the loop, and how its domain docs are laid out. Run once per consumer repo; bridges `executing-plans`, `feature-intake`, `prd-writer`, and `qa-reviewer` into a new repo. Prompt-driven, not deterministic. Explore first, present findings, confirm each decision, show drafts, then write. Never write speculatively. ## Contract Inputs: - Target repository: its git remote, existing `CLAUDE.md` / `AGENTS.md`, and `docs/agents/` - Existing label vocabulary and GitHub Projects board, read live via `gh` - User overrides for label strings, the project board number, and the domain layout Outputs: - A draft `## Agent skills` routing block - Draft `docs/agents/{issue-tracker,triage-labels,domain}.md` files seeded from `references/` - A short summary of present vs. missing routing state Creates/Modifies: - Writes the `## Agent skills` block into `CLAUDE.md` (preferred) or `AGENTS.md`, in place - Creates `docs/agents/*.md` from the reference seeds, updating in place when they already exist - Never creates a second routing file when one already exists, and never duplicates the block External Side Effects: - Reads git remote, GitHub labels, and project boards via read-only `gh` calls - Writes local files only; performs no GitHub mutations Confirmation Required: - Before writing the routing block or any `docs/agents/` file - Before choosing `CLAUDE