gds-create-game-brief

A game design brief should capture the core fantasy, target audience, scope, pillars, and MVP. This structured brief ensures your vision is focused and validated before drafting the full Game Design Document.

You can create a game brief through a guided elicitation workflow that refines your idea into a structured brief. This collaborative process outputs a brief.md and a decision log for downstream design work.

Yes, you can validate an existing game brief to ensure it correctly captures core vision, audience, and scope. The workflow reviews your brief and generates an audit trail to confirm production readiness.

Documenting game design decisions is best handled by generating a decision log alongside your brief. This auditable artifact tracks the rationale behind your scope and pillar choices for downstream production planning.

Yes, you can update a game brief using headless mode, which processes updates without interactive coaching. This allows automated refinement of your brief while still maintaining the structured YAML frontmatter and audit trails.

No, you do not need a completed MVP. The brief creation process helps define the MVP early by capturing core pillars and scope, ensuring your minimum viable product aligns with the target audience and core fantasy.