gds-create-game-brief

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

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-create-game-brief-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-create-game-brief
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-create-game-brief
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-create-game-brief-archaonhw

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 core fantasy stays vague. This Skill coaches you through discovery, drafts the brief, and pressure-tests it so downstream design work (GDD, PRD) starts from a solid foundation. ## 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 (one-sentence core fantasy, 2-4 pillars, specific audience, minimal MVP). - Discovery coaching: Brain-dump friendly questioning, web-research subagents for genre and market context, and a choice between a Fast path (assumption-tagged draft) or Coaching path (section-by-section pushback). - Persistent workspace: Writes brief.md, addendum.md, and .decision-log.md to a run folder, supports resume across sessions, headless JSON-status operation, and optional external handoffs (Confluence, Slack) via customization TOML. - Use Case: You have a pitch meeting tomorrow for a turn-based tactics game. Invoke the skill, brain-dump your concept, take the Fast path, and receive a polished brief.md with flagged assumptions to review. ## 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 choose Create intent. It runs a discovery conversation covering vision, audience, core loop, scope, and references, then drafts brief.md in a persistent run folder that the GDD workflow can build on.

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 audience is not "everyone", comparable titles name what is taken versus left, scope matches the team, and the MVP truly validates the core gameplay hypothesis.

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

Yes. Update mode reads the existing brief, addendum, and decision log, reconciles the change signal against prior decisions, and records every edit to .decision-log.md as an audit trail. Fundamental pivots trigger an offer to Create instead.

Does the game brief skill work headless or non-interactively?

Yes. In headless mode it infers intent, completes the work without prompting, and returns a JSON status block with artifact paths. If intent stays ambiguous it halts with a blocked status and reason.

What files does the game brief workflow produce?

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