gds-create-game-brief

Create, update, or validate game briefs through conversational coaching and structured drafting.

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill gds-create-game-brief-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-create-game-brief
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-create-game-brief
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-create-game-brief-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

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 producing, refining, or pressure-testing a game brief that downstream design work can build on. ## Core Features & Use Cases - Three intent modes: Create a new brief through guided discovery, 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). - Conversational discovery with research grounding: Brain-dump friendly elicitation with web-research subagents for genre landscape, comparable titles, and market context, plus Fast path and Coaching path working modes. - Persistent workspace and audit trail: Writes brief.md, addendum.md, and .decision-log.md to a run folder, supports resume across sessions, headless JSON operation, and external handoffs (e.g., Confluence) at finalize. - Use Case: You have a pitch meeting tomorrow. Invoke the skill, choose the Fast path, answer one consolidated batch of questions, and receive a polished brief.md with [ASSUMPTION] tags to review before the meeting. ## Quick Start Ask the assistant to help you create a game brief for your game idea and answer its discovery questions.

Frequently Asked Questions about gds-create-game-brief

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

FAQPage Schema
How do I create a game brief before writing a GDD?

Invoke the skill with your game idea and it will run a discovery conversation covering vision, target players, core loop, scope, and differentiation. It then drafts brief.md in a persistent run folder, which becomes the foundational input for the GDD step.

What makes a good game brief quality bar?

The skill validates that the core fantasy fits one sentence, pillars are 2-4 and specific, the core loop is clear, the audience is not "everyone", comparable titles are named with what is taken versus left, scope matches the team, and the MVP is truly minimal.

Can I update an existing game brief instead of starting over?

Yes, the Update intent reconciles an existing brief with a change signal after reading the brief, addendum, and decision log. Every change and its reasoning is recorded to .decision-log.md as a mandatory audit trail.

Does the game brief skill work in headless or non-interactive mode?

Yes, headless mode completes the detected intent without prompting and returns a JSON status block with artifact paths. If intent is ambiguous, it halts with a blocked status and reason instead of asking questions.

What files does the game brief workflow produce?

It produces brief.md with YAML frontmatter, an optional addendum.md for downstream detail, and a .decision-log.md audit trail, all inside a run folder under the configured briefs output path.