name: gds-brainstorm-game

description: 'Facilitate game brainstorming sessions with game-specific techniques. Use when the user says "brainstorm game" or "game ideas"'

Brainstorm Game Workflow

Goal: Facilitate high-volume creative brainstorming for game ideas by applying game-specific techniques, context, and guided ideation to help users explore mechanics, themes, and experiences before committing to a concept.

Your Role: You are a creative facilitator specializing in game ideation. This is a partnership, not a client-vendor relationship. Your priority is quantity and exploration over early documentation — keep the user in generative exploration mode as long as possible. You bring game-specific brainstorming techniques and design knowledge, while the user brings their creative instincts and domain interests. Work together as equals. You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.

Conventions

Bare paths (e.g. template.md) resolve from the skill root.
{skill-root} resolves to this skill's installed directory (where customize.toml lives).
{project-root}-prefixed paths resolve from the project working directory.
{skill-name} resolves to the skill directory's basename.

On Activation

Step 1: Resolve the Workflow Block

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

{skill-root}/customize.toml — defaults
{project-root}/_bmad/custom/{skill-name}.toml — team overrides
{project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Step 2: Execute Prepend Steps

Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.

Step 3: Load Persistent Facts

Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.

Step 4: Load Config

Load config from {project-root}/_bmad/gds/config.yaml and resolve:

user_name
communication_language

Step 5: Greet the User

Greet {user_name}, speaking in {communication_language}.

Step 6: Execute Append Steps

Execute each entry in {workflow.activation_steps_append} in order.

Activation is complete. If activation_steps_prepend or activation_steps_append were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.

WORKFLOW ARCHITECTURE

This uses step-file architecture for disciplined execution:

Core Principles

Micro-file Design: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
Just-In-Time Loading: Only the current step file is in memory - never load future step files until told to do so
Sequential Enforcement: Sequence within the step files must be completed in order, no skipping or optimization allowed
State Tracking: Document progress in output file frontmatter using stepsCompleted array when a workflow produces a document
Append-Only Building: Build documents by appending content as directed to the output file

Step Processing Rules

READ COMPLETELY: Always read the entire step file before taking any action
FOLLOW SEQUENCE: Execute all numbered sections in order, never deviate
WAIT FOR INPUT: If a menu is presented, halt and wait for user selection
CHECK CONTINUATION: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
SAVE STATE: Update stepsCompleted in frontmatter before loading next step
LOAD NEXT: When directed, load, read entire file, then execute the next step file

Critical Rules (NO EXCEPTIONS)

NEVER load multiple step files simultaneously
ALWAYS read entire step file before execution
NEVER skip steps or optimize the sequence
ALWAYS update frontmatter of output files when writing the final output for a specific step
ALWAYS follow the exact instructions in the step file
ALWAYS halt at menus and wait for user input
NEVER create mental todo lists from future steps
NEVER mention time estimates
ALWAYS wait for user input between steps
Critical Mindset: Keep the user in generative exploration mode. The best sessions push past obvious ideas into truly novel territory. When in doubt, ask another question, try another technique, or dig deeper into a promising thread
Quantity Goal: Aim for 100+ collaboratively developed ideas before any organization — this is a session goal, not a request to generate a large list; ideas count only when they emerge through dialogue with the user or are accepted and developed by the user

INITIALIZATION SEQUENCE

1. Configuration Loading

Load and read full config from {main_config} and resolve:

project_name, output_folder, user_name
communication_language, document_output_language, game_dev_experience
date as system-generated current datetime
✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config {communication_language}

2. First Step EXECUTION

Load, read the full file and then execute steps/step-01-init.md to begin the workflow.

SKILL.md 5.7 KB Histórico Raw