brainstorm
/brainstorm
Guides the user through finding and choosing a game concept. Use when the user wants game ideas, a new concept, a game jam idea, or to explore other directions, including dropping the current idea and starting over.
- Author
- wyx135230 ↗
- Repository
- Codex-Game-Studios ↗
- Licence
- MIT
- Last repository change
- 03.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Guides the user through finding and choosing a game concept. Use when the user wants game ideas, a new concept, a game jam idea, or to explore other directions, including dropping the current idea and starting over.
Original author description
Guides the user through finding and choosing a game concept. Use when the user wants game ideas, a new concept, a game jam idea, or to explore other directions, including dropping the current idea and starting over.
How it works
- Lean Brief flow (workflow: minimal)
SKILL.md preview
---
name: brainstorm
description: "Guides the user through finding and choosing a game concept. Use when the user wants game ideas, a new concept, a game jam idea, or to explore other directions, including dropping the current idea and starting over."
---
Read `.codex/docs/runtime.md` before executing this workflow. Arguments are the text following the skill invocation; substitute them where `$ARGUMENTS` appears.
Before proceeding, run this command from the repository root and use its output:
```bash
bash ".codex/hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,docs.density,workflow
```
Resolved above; use as-is. No block → the defaults in `.codex/docs/config-resolution.md`
(`workflow: minimal`, `review_mode: solo`, `automation: collaborative`, `docs.density: terse`), and
say that the settings were not read.
# Brainstorm
Turns no idea, or a rough one, into a written design the next step builds from. How much it writes
depends on `workflow`:
- **`minimal`:** the Lean Brief flow below: a one-page `design/game-brief.md`, then stop. No
discovery questions, pillars, director gates or `game-concept.md`, and do not load
`references/full-concept.md`.
- **`standard` or `full`:** read `references/full-concept.md` and follow it. It writes
`design/gdd/game-concept.md` from `.codex/docs/templates/game-concept.md`. Its gates follow
`.codex/docs/director-gates.md`; each director agent is given its own gate file,
`.codex/docs/director-gates/<gate-id in lower case>.md` (`cd-pillars.md`,
`ad-concept-visual.md`, `td-feasibility.md`, `pr-scope.md`), and you do not read those files
yourself.
`--review` in the text typed after the skill name overrides `review_mode` for this run.
`docs.density` sets each section's depth: `terse` = bullets; `balanced` = with brief rationale;
`thorough` = rationale and alternatives. Questions follow `.codex/docs/automation-modes.md`
(collaborative asks, guided asks only for major decisions, autonomous logs and proceeds; the
always-ask categories always ask).
Ask with the question tool. Without one, list the options numbered and end your turn to wait. The
question is the last thing in the reply: no advice or lean after it. A skipped or dismissed
question is not an answer: ask again in plain text.
## Lean Brief flow (`workflow: minimal`)
A few exchanges, not fifteen: capture the thinking that carries the game on one page, then get to
code. Write from the template `.codex/docs/templates/game-brief.md` (six required fields, three
one-liners). If `design/game-brief.md` exists, read it and refine it instead of starting over.
1. **Concept.** From the hint typed after the skill name (or one quick open question if there is
none), propose **2 or 3 one-line concepts** (verb-first or a mashup of genre and theme), not
full concept cards. Ask the user to pick or combine them. This is the one creative question
every run asks.
2. **Fill the brief** in conversation, several fields per exchange:
- **Working title:** the brief's title line. Offer one from the chosen concept and let the user
change it; `/create-stories` names the epic folder after it.
- **Pitch:** the excited one-liner.
- **Core loop:** the 2 to 4 steps the player repeats.
- **Player goal & fail state**: what the player tries to do, and how they lose.
`/create-stories` turns it into acceptance criteria.
- **MVP:** the short list that makes it the game; each item becomes a story. **More than 7
items: push back.** Say it is too long for an MVP, propose which items to cut (the ones the
core loop works without), and keep the brief to 7 or fewer.
- **Out of scope:** what they are deliberately not building (the cut items go here).
- **Build order:** the riskiest or least proven part first.
- **Who it's for and what they feel**, **Art & audio direction**, **Reference game** (the
closest shipped game, and the part of it the MVP keeps): one line each; offer, don't force.
3. **Show the filled brief in full.** Then ask, as its own question: "Brief is ready. May I write it
to `design/game-brief.md`?" `Yes — write it` / `Revise a field first`. Write only on an explicit
yes to this question; agreeing to a cut or saying "go on" is not a yes to the write. On a
revision, change the named field, show it before and after, and ask again. Then write
`design/game-brief.md`, creating folders as needed. Never write `design/gdd/game-concept.md`
at this tier.
4. **Next steps.** Read `engine.name` in `project.yaml`:
1. `/setup-engine`: configure the engine. List it **only** when `engine.name` is absent or
empty: on the minimal path it usually ran before this skill.
2. `/create-stories`: turn the MVP list into stories. At `minimal` there is no separate
`/create-epics` or `/sprint-plan`; the build order is the plan.
3. `/dev-story`: the first line of game code.
Then one summary line: the pitch, the number of MVP items, and `design/game-brief.md`. End with
the line `Verdict: COMPLETE — game brief written; next stop is code.`
If the user stops before the write, say the brief was not written, so it lives only in this
conversation.
Files in this package (2)
- SKILL.md 5 KB
- references/full-concept.md 12 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · wyx135230/Codex-Game-Studios | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| vanducng/skills | 100 | MIT |
| Kanevry/session-orchestrator | 100 | MIT |
| nigelng/nng-kit | 100 | MIT |
| joris887/exosuit | 100 | MIT |
| duronext/jig | 100 | MIT |
| verygoodopensource/vgv-wingspan | 100 | MIT |
Database snapshot: 13.11.2026 · package version 171c18d1ca5a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100game-brainstorm
Runs designer-led ideation that turns a mood, theme, genre or "something like X" into three original concepts and one chosen Game Concept Document with core loop, pillars, player fit and scope, plus 5-10 minute web or jam hooks. Use for "game idea", "brainstorm", "pitch", "what… - 100rbx-concept
Roblox: brainstorm game ideas or write a one-page concept brief with a QPTR story and kill criteria. Use for new ideas, pivots, 'is this idea good'. - 90game-idea
Turn no idea, a rough idea, or a big dream into a small game that can actually be finished, written down as a one-page game-brief.md. Use when someone wants game ideas, wants to plan their game, says their idea is too big, or wants to start over with a new idea. - 100paw-ps-discovery
Creative discovery partner for ideation and concept shaping. Use when brainstorming, exploring product ideas, expanding vague concepts, comparing directions, finding opportunities, creative ideation. Triggers: 'brainstorm', 'product ideas', 'concept exploration', 'idea… - 95unikit-gd-brainstorm
Ideate a brand-new game concept with the user, from a blank page or a one-line hint to a finished CONCEPT card. Use it whenever the user wants to come up with a new game — whether the project has no design document yet, or already has one and they're exploring a fresh idea.… - 90game-forge
End-to-end workflow for making a video game of any kind, in any engine (Godot, Unity, Unreal, LÖVE, Phaser/web, Pygame, Bevy, MonoGame or none), starting from a design brief the user fills in. Use this skill whenever someone wants to make, start, prototype, plan or continue…