SGDK planning

Help the developer choose the next playable proof, understand its hardware risks, and leave room for the game to grow. Produce a useful plan for an ordinary SGDK project, not a new engine or a generic game-design document.

Find the smallest useful proof

Read the request and existing project decisions first. Ask only about choices that materially change the initial proof, such as the core mechanic, target region, simultaneous players or a required cartridge. Record reversible assumptions and proceed instead of making the developer answer a fixed survey.

Describe what the player will see and do in the first milestone, including how to tell whether it works. Keep the intended game recognizable while reducing content. A scrolling game needs an early scrolling proof; a busy shooter needs an early crowded-screen proof. An empty screen reaching 60 Hz proves neither.