designlisted

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Write a game design document. This is the FIRST step in the qq pipeline — it produces the design doc that `/qq:plan` turns into a technical implementation plan. Arguments: $ARGUMENTS ## Language boundary (HARD RULE) This skill writes **game design**, not technical architecture. Explore the codebase to understand what exists, but translate everything into player-facing language. | Write this (design language) | NOT this (implementation language) | |---|---| | 游戏流程管理 | `DemoGameManager` | | 船员会感到饥饿和疲劳 | `CrewNeeds.Hunger`, `NeedsTickSystem` | | 工作台可以制作物品 | `ProductionComponent`, `ITaskIssuer` | | 船员前往火炮并操控 | `Task_OperateTurret`, `MannedWeaponComponent` | | 食物保鲜随时间下降 | `ItemProperty.Freshness float decay` | **Self-check before saving:** scan the document for `.cs`, `Manager`, `Component`, `System`, `Service/`, `class`, `interface`, `MonoSingleton`. If found, replace with design language. ## Output structure ```markdown # [Feature Name] Design Document ## 1. Problem & Goal What gap this addresses. What the player experience looks like when done. (2-3 sentences) ## 2. Reference Games | Game | How they do it | What we borrow | ## 3. Design Approach Which approach was chosen and why. One sentence on trade-offs if relevant. ## 4. Detailed Design - Player-facing state/flow (ASCII or Mermaid diagram) - Game concept definitions (describe what the