setup-chiptus-env
Setup Chiptus Env
In order: confirm setup-matt-pocock-skills is installed, run it to pick this repo's issue tracker (and the triage labels, domain docs it also configures), offer to relocate docs/agents/ (and domain docs) to an external folder for repos that can't keep them in-repo, then scaffold the autonomic issue pipeline — docs/agents/autonomic-issues.md — templated to that same tracker. The pipeline step reuses the tracker choice setup-matt-pocock-skills already made; never ask which tracker twice.
Process
1. Check setup-matt-pocock-skills is installed
Check for a setup-matt-pocock-skills folder under .claude/skills/ or .agents/skills/ — locally, or globally per whatever install location the dev is using (ask if unclear). Present → continue to step 2.
Missing → don't install it yourself. How and where to install it (per-repo vs. global machine-wide, plugin vs. npx skills add) is the dev's call, not this skill's — installing on their behalf risks the wrong scope or clobbering an existing setup. Tell the dev it's missing, give them the install command (npx skills add <setup-matt-pocock-skills package> -s "*" -a claude-code -y --json — note the agent identifier is claude-code, not claude; the latter is rejected by the CLI) or point at the plugin marketplace flow, and stop. Resume at step 2 once they confirm it's installed.
2. Run setup-matt-pocock-skills
Invoke the setup-matt-pocock-skills skill and let it run to completion (issue tracker, triage labels, domain docs, its own ## Agent skills block). Its Section A answer is the tracker this skill scaffolds the pipeline for — read it back from docs/agents/issue-tracker.md (its heading names the tracker: GitHub, GitLab, Local, or the freeform "other" description) rather than asking again.
If Section B (triage labels) is running and the tracker is GitHub, suggest naming the five labels with a triage/ prefix (triage/needs-triage, triage/ready-for-agent, …) when it asks whether to keep the defaults — this repo's convention is / as the delimiter for every prefixed label, matching priority/*, agent/*, etc. (see references/github.md). This is a plain naming choice for consistency, not a GitHub grouping feature — GitHub renders / no differently than any other character. Still the user's call; don't override a "keep defaults" answer.