setup-developer-skillslisted

# Setup Developer Skills Scaffold the per-repo configuration that the `/developer` pipeline assumes. This builds **on top of** Matt Pocock's engineering skills setup — it does not replace it. Two independent axes get configured, mirroring how the delivery skills read the repo: - **Issue tracker** — where issues live (`docs/agents/issue-tracker.md`, created by Matt's setup; this skill appends the pipeline's `## Delivery operations` section). - **Code host** — where changes (PRs/MRs/branches) live (`docs/agents/code-host.md`, created here). They may differ (issues in Linear, code on GitHub). **GitHub, GitLab and local are first-class** — templates ship with this skill. Anything else (Jira, Linear, Gitea…) is configured as freeform prose, exactly like Matt's setup handles "other" trackers. This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write. ## Process ### 1. Preconditions - **Matt Pocock's setup must have run first**: check whether `docs/agents/issue-tracker.md` exists. If it does not, **stop — scaffold nothing**. Matt's `setup-matt-pocock-skills` declares `disable-model-invocation: true`, so you cannot run it on the user's behalf; only the user can, as a slash command. Tell them: > This repo isn't configured yet. Run `/setup-matt-pocock-skills` first > (namespaced as `/mattpocock-skills:setup-matt-pocock-skills` when > installed as a plugin), then re-run `/setup-developer-ski