What problem does it solve? Turning a raw game idea into a clear, right-sized game brief is hard: assumptions go unexamined, scope balloons, and the resulting document fails as a foundation for the Game Design Document. This Skill coaches you through discovery, drafting, and validation so the brief captures the core vision honestly. ## Core Features & Use Cases - Three intent modes: Create a new brief from conversation, Update an existing brief against a change signal with a mandatory decision log, or Validate a brief against a quality bar (single-sentence core fantasy, 2-4 pillars, clear core loop, minimal MVP). - Guided discovery: Surfaces vision, target players, core loop, scope, references, and differentiation through coaching dialogue, with fast-path and coaching-path working modes. - Persistent workspace: Writes brief.md, addendum.md, and .decision-log.md to a run folder, supports resume across sessions, and runs polish passes and reviewer gates at finalize. - Use Case: You have a pitch for a roguelike deckbuilder due tomorrow. Invoke the skill, choose the fast path, answer one consolidated batch of questions, and receive a polished brief with [ASSUMPTION] tags to review. ## Quick Start Ask the assistant to help you create a game brief for your game idea using the gds-create-game-brief skill.
