メニュー
Interview the user relentlessly about a game design concept or design until reaching shared understanding, stress-testing the concept and resolving each branch of the decision tree.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | grill-gamedesign |
| description | Interview the user relentlessly about a game design concept or design until reaching shared understanding, stress-testing the concept and resolving each branch of the decision tree. |
Interview me relentlessly about every aspect of the Markdown game design document attached, until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. Actively consult other game design documents to ensure that there are no conflicts or missing information.
Though you can read existing code, THIS IS NOT A CODING SESSION. We are building a game design document ONLY.
For each question, provide your recommended answer. Ask the questions one at a time.
At the end, update, rewrite or restructure the Markdown document properly with the decisions made.
For each subsection in the document, apply the following structure.
The four buckets track implementation status, not just decision certainty — the document doubles as a progress tracker.
Keep all four headings present even when empty, writing _None._ under the
empty ones, so what is not yet done stays visible. List them in this pipeline order:
## Subsection Title
### Implemented
Decisions that are built and working in the codebase today.
Respecting these is crucial to the general game's architecture.
### In progress
Big undertakings that are decided and already have committed roots in the source, but still have
work left.
State what has landed and what remains, so the bucket reads as a progress entry, not just a decision.
These are important to the general game's architecture and must be considered in every existing or
future implementation.
### To do
Ideas that we decided on but have not built yet — no implementation, or only a reserved stub.
Those are important to the general game's architecture and must be considered in every existing or
future implementation.
They may exist in some preparatory state in the current codebase to avoid future blockers and major
refactoring.
### Exploratory
Ideas mentioned that we couldn't reach a final decision on yet, but to keep in mind in every future
iteration.
They may or may not exist as some prototyping implementation.
Drive and read Ionwake's `__ionwake*` window instrumentation hooks (`__ionwakeScene` on /play, `__ionwakeShipyard` on /shipyard, and the dev-only `__ionwake` debug flags) from outside the page via the Chrome DevTools MCP. Use to read live sim/scene/clock state, screenshot the running app, drive the shipyard, load ship models, inspect a ship schema, log the WebTransport wire, or keep a backgrounded tab stepping.
Compact the current conversation into a handoff document for another agent to pick up.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.