fix(skills): recognize all team branches in sprint skills

start-sprint and plan-sprint only recognized server/client as valid team
branches. Updated to include all six teams (server, client, copy, audio,
visual, ci) matching the SI agent's ticket assignment rules.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/skills/plan-sprint/SKILL.md

@@ -12,8 +12,10 @@ allowed-tools: Bash, Read, Grep, Glob, Write, AskUserQuestion
 
 # Plan Sprint
 
-Generate sprint briefing files (`server.md`, `client.md`, `joint.md`) for the
-next sprint based on current project state.
+Generate sprint briefing files for each active team (e.g. `server.md`,
+`client.md`, `copy.md`, `joint.md`) for the next sprint based on current
+project state. Valid teams: `server`, `client`, `copy`, `audio`, `visual`,
+`ci`. Only generate briefings for teams that have tickets in the sprint.
 
 ## Workflow
 
@@ -102,9 +104,16 @@ Key requirements per file:
 - **server.md**: Carry-overs, new tickets, dependency chain, key decisions, notes
   referencing existing Rust modules by path
 - **client.md**: Same structure, notes referencing existing GDScript files by path
+- **copy.md**: In-game text tasks — dialogue, UI copy, tooltips, flavor text, lore
+- **audio.md**: Sound design, music, audio integration tasks
+- **visual.md**: Art direction, asset creation, visual consistency tasks
+- **ci.md**: Build pipeline, CI/CD, tooling, infrastructure tasks
 - **joint.md**: Pre-sprint decisions table, integration tickets, sprint
   completion proof (concrete observable criteria), test plan alignment
 
+Only generate briefing files for teams that have tickets assigned in the sprint.
+Not every sprint will have work for every team.
+
 ### 8. Assign tickets to sprint in DB
 
 After the user approves, assign all selected tickets to the new sprint:

.claude/skills/start-sprint/SKILL.md

@@ -2,9 +2,9 @@
 name: start-sprint
 description: >
   Start sprint work on a team branch. Use when the user says "start sprint",
-  "start working on the server/client", "begin sprint", or invokes /start-sprint.
-  Merges main into the team branch, finds the active sprint, reads the sprint
-  briefing, and presents the work plan with ticket details.
+  "start working on the server/client/copy", "begin sprint", or invokes
+  /start-sprint. Merges main into the team branch, finds the active sprint,
+  reads the sprint briefing, and presents the work plan with ticket details.
 user-invocable: true
 allowed-tools: Bash, Read, Grep, Glob
 ---
@@ -41,8 +41,8 @@ The current branch IS the team. Read it with:
 git branch --show-current
 ```
 
-Valid team branches: `server`, `client`. If on `main`, ask the user which
-team branch to check out first.
+Valid team branches: `server`, `client`, `copy`, `audio`, `visual`, `ci`.
+If on `main`, ask the user which team branch to check out first.
 
 ### 2. Sync with main
 
@@ -65,8 +65,9 @@ report that and stop.
 ### 4. Read the sprint briefing
 
 Read `$REPO_ROOT/docs/sprints/sprint-N/<team>.md` where N is the sprint ID
-and team matches the branch name. If the branch is `server` or `client`, use
-that directly. For other branches, check if a matching briefing exists.
+and team matches the branch name (e.g. `server.md`, `client.md`, `copy.md`).
+If no matching briefing exists for the team, report that and suggest running
+`/plan-sprint` to generate one.
 
 Also check for a `joint.md` briefing — joint tasks involve both teams and
 should be mentioned.

CLAUDE.md

@@ -19,7 +19,7 @@ docs/
   briefings/          # Per-agent context briefings (maintained by Qatux)
   architecture/       # Technical architecture documents
   design/             # Game design documents
-  sprints/            # Sprint briefings per team (server.md, client.md, joint.md, content.md)
+  sprints/            # Sprint briefings per team (server.md, client.md, copy.md, joint.md, etc.)
   workshops/          # Workshop briefs and outputs (per-workshop subdirectories)
 db/
   commonwealth.db     # SQLite ticketing database