跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

brainstorm

Guided concept ideation using professional studio techniques, player psychology, creative exploration.

Donchitos · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Donchitos/Claude-Code-Game-Studios --skill brainstorm

技能说明


name: brainstorm description: "Guided concept ideation using professional studio techniques, player psychology, creative exploration." argument-hint: "[genre or theme hint, or 'open'] [--review full|lean|solo]" user-invocable: true allowed-tools: Read, Glob, Grep, Write, WebSearch, Agent, AskUserQuestion model: sonnet

!source "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/yaml-helper.sh" 2>/dev/null && resolve_config --keys review_mode,automation,docs.density,workflow

Resolved above — use as-is. No block → defaults in .claude/docs/config-resolution.md.

--review overrides review_mode; store it for all gate spawns this run. See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md — the spawned agent reads its own gate file; do not read it in the parent session.

Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

docs.density — it controls per-section depth, where workflow controls which sections exist. modes.rigor sets both together; set docs.density explicitly to vary depth alone: terse = pillar bullets + concept bullets; balanced = pillars + concept with brief rationale (default); thorough = pillars + concept + extensive rationale + alternatives. Apply it to every section you author.


Tier branch — check workflow FIRST

The workflow tier resolved above governs this skill's output:

  • standard / full → run the full flow ("When this skill is invoked" through Phase 5 and the concept-document generation). No change.
  • minimal → run the Lean Brief flow immediately below and STOP — skip Phases 1–5, the director gates (CD-PILLARS / AD-CONCEPT-VISUAL / TD-FEASIBILITY / PR-SCOPE), and the full-length concept document entirely. Output is the one-page design/game-brief.md, not game-concept.md.

Lean Brief flow (workflow: minimal only)

A jam / small-scope session: capture the load-bearing thinking in one page, then get to code. Keep prompting light — a few exchanges, not fifteen. Author from the one-page template .claude/docs/templates/game-brief.md (6 required fields + 2 one-liners). If design/game-brief.md already exists, read it and resume/refine rather than restart.

  1. Concept — from the argument hint (or one quick open question if none), propose 2–3 one-line concepts (verb-first or mashup, per Phase 2's techniques). One AskUserQuestion to pick or combine — the only guaranteed creative prompt.

  2. Fill the brief fields conversationally (not one prompt each):

    • One-sentence pitch — the excited one-liner.
    • Core loop — the 2–4 step cycle the player repeats.
    • MVP — the ruthlessly short feature list that makes it the game (each becomes a story downstream). If it runs past ~7, push back on scope.
    • Out of scope — what they're deliberately NOT building.
    • Build order — sequence to build the MVP, risky / core-fun thing first.
    • Who it's for / what they feel and Art & audio direction — one line each (offer, don't force). Present the filled brief back in full for a single confirmation.
  3. Write approval — AskUserQuestion: "Brief is ready. May I write it to design/game-brief.md?" → [A] Yes — write it / [B] Revise a field first. On [B], revise the named field, show before/after, re-ask; repeat until [A]. Then write design/game-brief.md from the template, creating directories as needed. Honor modes.automation for this write as elsewhere in the framework.

  4. Next steps (short — this is the point). Read engine.name from project.yaml first and list /setup-engine only if it is absent or empty:

    1. (only when engine.name is absent or empty) "/setup-engine — configure the engine (required before code)"
    2. "/create-stories — turn the brief's MVP list into implementable stories. The epic is implicit at minimal; there is no separate /create-epics or /sprint-plan — the brief's build order is the plan."
    3. "/dev-story — first line of game code"

    Why the condition. /start's minimal path runs /setup-engine before /brainstorm, and /setup-engine Section 2 states that a missing brief is expected because the brief is authored afterwards. Listing engine setup unconditionally here tells a user who just followed that path to go back and redo step one — the only skill in the four-step path that assumes it runs first. Then output a one-line summary (pitch + MVP feature count + design/game-brief.md).

Verdict: COMPLETE — game brief created; next stop is code. Do NOT run Phases 1–5, spawn any director gate, or write game-concept.md at this tier.


When this skill is invoked (standard / full tier — minimal uses the Lean Brief flow above):

  1. Parse the argument for an optional genre/theme hint (e.g., roguelike, space survival, cozy farming). If open or no argument, start from scratch.

  2. Check for existing concept work:

    • Read design/gdd/game-concept.md if it exists (resume, don't restart)
    • Read design/gdd/game-pillars.md if it exists (build on established pillars)
  3. Run through ideation phases interactively, asking the user questions at each phase. Do NOT generate everything silently — the goal is collaborative exploration where the AI acts as a creative facilitator, not a replacement for the human's vision.

    Use AskUserQuestion at key decision points throughout brainstorming:

    • Constrained taste questions (genre preferences, scope, team size)
    • Concept selection ("Which 2-3 concepts resonate?") after presenting options
    • Direction choices ("Develop further, explore more, or prototype?")
    • Pillar ranking
阅读完整来源 ↗