team-level

When this skill is invoked: **Decision Points:** At each step transition, use `question` to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next step. 1. **Read the argument** for the target level or area (e.g., `tutorial`, `forest dungeon`, `hub town`, `final boss arena`). 2. **Gather context**: - Read the game concept at `design/gdd/game-concept.md` - Read game pillars at `design/gdd/game-pillars.md` - Read existing level docs in `design/levels/` - Read relevant narrative docs in `design/narrative/` - Read world-building docs for the area's region/faction ## How to Delegate Use the Task tool to spawn each team member as a subagent: - `subagent_type: narrative-director` — Narrative purpose, characters, emotional arc - `subagent_type: world-builder` — Lore context, environmental storytelling, world rules - `subagent_type: level-designer` — Spatial layout, pacing, encounters, navigation - `subagent_type: systems-designer` — Enemy compositions, loot tables, difficulty balance - `subagent_type: art-director` — Visual theme, color palette, lighting, asset requirements - `subagent_type: accessibility-specialist` — Navigation clarity, colorblind safety, cognitive load - `subagent_type: qa-tester` — Test cases, boundary testing, playtest checklist Always provide full context in each agent's prompt (ga...