Godot Grill

Settle the decisions only the developer can make, before anyone designs a scene tree or writes code. The output is a decision record, not a design.

Related skills: gecs-core for primitives, gecs-systems for cmd CommandBuffer mutations, gecs-queries for state filtering, gecs-observers for .on_match()/.on_unmatch() state enter/exit triggers.

1. Decisions, not facts

Ask only what only the user knows: intent, constraints, priorities, taste.

Node types, API signatures, and version differences are facts. Look them up (godot-brainstorming/references/node-selection.md, the domain skills), decide, and record the choice. Never spend a question on one.

Architecture choices — data home, state representation, save format — are decided from the user's answers, not asked as technology picks. Ask the constraint behind them ("will designers edit items in the Inspector?"), then map the answer to Resource .tres yourself.