Preset Game Bible tickets
Fill in your game spec, then work through the tickets in dependency order. Select a ticket to download its Markdown file.
| Chapter | Ticket | Blocked by | What to demonstrate |
|---|---|---|---|
| 01 | Define the first release | None | The owner can explain the player promise, audience, target, and first playable. |
| 02 | Specify the game loop and scenes | 01 | The core loop has observable rules and a rough scene roadmap. |
| 03 | Run the first interaction on the target | 02 | A fresh checkout runs a representative interaction using its assets. |
| 04 | Prove the mechanics in the sandbox | 03 | Required rules, inputs, and recovery can be exercised from known states. |
| 05 | Assemble and playtest each scene | 04 | A player can enter, complete, and exit each in-scope scene. |
| 06 | Write and verify player help | 05 | A fresh player can find and use help that matches the build. |
| 07 | Verify the release candidate | 06 | The exact candidate works from the planned delivery entry point. |
| 08 | Walk a new contributor through a change | 07 | A contributor can run, change, and verify the released workflow. |
| 09 | Rehearse or deliver an update | 08 | One change goes through the affected checks and documentation. |
| 10 | Review feedback and plan the next cycle | 09 | Feedback reaches an owner and produces a next-cycle scope decision. |