This is part 2 of my Hex Reverse development diary.
One of the main things I focused on was avoiding implementation based only on the latest conversation, and preventing AI tools from touching more of the project than intended.
I first prepared the game design, then worked with ChatGPT to organize repository-based Markdown documents for specifications, task lists, and change tracking. The work was divided into phases and tasks, with boundaries between what Codex could edit directly and what I would handle in the Unity Editor.
From there, I began implementing the game from a minimal battle prototype. The recurring workflow was: organize the next task with ChatGPT, implement it with Codex, review the result, and test it in Unity when needed.
The plan also evolved during development, with phases and tasks being added or split as the project grew.
Full article
The full article explains the documents, workflow, and implementation process in more detail.
The linked article is in Japanese.
Posted by the game’s developer or publisher to its Steam community hub and published by Valve through Steam’s public news API. Sifter reproduces it unedited and writes none of it.