gds-create-game-brief

Guide step-by-step game brief creation with frontmatter-driven workflow states.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-create-game-brief-joekhosbayar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-create-game-brief
Source: https://github.com/joekhosbayar/go-mighty/tree/main/.gemini/skills/gds-create-game-brief
Command: npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-create-game-brief-joekhosbayar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically craft Game Briefs by guiding discovery, documenting decisions, and aligning stakeholders.

Core Features & Use Cases

  • Guided elicitation and collaboration steps for game briefs
  • Templates and progressive steps to structure vision, market, and scope
  • Handoff-ready outputs to feed into GDD workflows

Quick Start

Provide your game's working title and a brief concept to begin the Game Brief workflow.

Frequently Asked Questions about gds-create-game-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a game brief and when do I need one before starting game design?

A game brief structures your game concept, market positioning, and scope. You need one during early-stage game design to align designers, writers, and stakeholders on a shared vision before creating a full Game Design Document (GDD).

How do I create a game brief for my game concept?

Create a game brief using a guided, step-by-step workflow that elicits your working title and concept. The process applies progressive templates to document decisions, structure vision, market, and scope, ensuring aligned team collaboration.

Does this game brief workflow support team collaboration and stakeholder alignment?

Yes, the game brief workflow supports team collaboration through stepwise collaboration menus and frontmatter-driven workflow states. It guides discovery and documents decisions to keep designers, writers, and stakeholders aligned throughout the process.

What's the best way to transition a game brief into a Game Design Document?

The best way to transition is to use handoff-ready outputs generated by the brief workflow. These structured outputs feed directly into downstream GDD workflows, ensuring foundational vision and scope decisions carry forward.

Can I use this guided brief creation process for early-stage game development?

Yes, this guided brief creation process is designed for early-stage game development. It helps teams structure and socialize a game concept through step-by-step brief creation before committing to full GDD documentation.