Add setup-matt-pocock-skills; rename github-triage to triage; migrate engineering skills to vague prose

Engineering skills no longer hard-code GitHub or specific label strings.
A new setup skill scaffolds an `## Agent skills` block in
AGENTS.md/CLAUDE.md plus `docs/agents/` so each repo can declare its own
backlog backend, triage label vocabulary, and domain doc layout. Skills
that need the mapping (to-issues, to-prd, triage) point at the setup
skill; skills that only soften with it (diagnose, tdd,
improve-codebase-architecture, zoom-out) stay vague. ADR-0001 records
the split.

Closes #88, #89.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

skills/engineering/to-issues/SKILL.md

@@ -1,21 +1,23 @@
 ---
 name: to-issues
-description: Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
+description: Break a plan, spec, or PRD into independently-grabbable issues on the project backlog using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
 ---
 
 # To Issues
 
-Break a plan into independently-grabbable GitHub issues using vertical slices (tracer bullets).
+Break a plan into independently-grabbable backlog issues using vertical slices (tracer bullets).
+
+The backlog backend and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
 
 ## Process
 
 ### 1. Gather context
 
-Work from whatever is already in the conversation context. If the user passes a GitHub issue number or URL as an argument, fetch it with `gh issue view <number>` (with comments).
+Work from whatever is already in the conversation context. If the user passes a backlog ticket reference (issue number, URL, or path) as an argument, fetch it from the backlog and read its full body and comments.
 
 ### 2. Explore the codebase (optional)
 
-If you have not already explored the codebase, do so to understand the current state of the code. Before exploring, follow [../grill-with-docs/DOMAIN-AWARENESS.md](../grill-with-docs/DOMAIN-AWARENESS.md). Issue titles and descriptions should use the project's `CONTEXT.md` vocabulary.
+If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
 
 ### 3. Draft vertical slices
 
@@ -47,16 +49,16 @@ Ask the user:
 
 Iterate until the user approves the breakdown.
 
-### 5. Create the GitHub issues
+### 5. Publish the issues to the backlog
 
-For each approved slice, create a GitHub issue using `gh issue create`. Use the issue body template below.
+For each approved slice, publish a new issue to the backlog. Use the issue body template below. Apply the `needs-triage` triage label so each issue enters the normal triage flow.
 
-Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.
+Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
 
 <issue-template>
 ## Parent
 
-#<parent-issue-number> (if the source was a GitHub issue, otherwise omit this section)
+A reference to the parent ticket on the backlog (if the source was a backlog ticket, otherwise omit this section).
 
 ## What to build
 
@@ -70,7 +72,7 @@ A concise description of this vertical slice. Describe the end-to-end behavior,
 
 ## Blocked by
 
-- Blocked by #<issue-number> (if any)
+- A reference to the blocking ticket (if any)
 
 Or "None - can start immediately" if no blockers.