The Office Escape Project Report
1. The Concept
The Office Escape is a lightweight, web-based endless jumping game designed for quick casual play. I chose an office-themed vertical escape game for this one-day sprint because it was simple enough to build in vanilla web technology, but still challenging enough to test gameplay logic, visual design, asset handling, and AI-assisted handoff work.
2. The Stack
The Stack: HTML5, Vanilla CSS, JavaScript, and Canvas.
The AI Assist: ChatGPT-4o handled the initial game planning, feature breakdown, and technical handoff document. OpenAI Codex was then used for the coding phase, turning the markdown handoff into a playable browser game with menu screens, platform generation, collectibles, boss chase behavior, and local saved settings.
3. The 1 Day Sprint:
Morning (Hours 1–3): We started by brainstorming small game ideas that could be completed quickly but still feel fun. We settled on an office escape platformer because it had a clear theme and simple controls. The first hours were spent defining the game loop, player movement, collectible types, boss behavior, and the required screens.
Afternoon (Hours 4–6): The coding phase began. Codex built the main project inside a single index.html file using Canvas, CSS, and JavaScript. The core gameplay came together quickly: the player auto-jumps, platforms generate endlessly, collectibles appear, and the boss rises from the bottom of the screen. Most of the time was spent adjusting the visual layout and making the game feel closer to the cartoon office style from the handoff.
The Finish Line (Hour 7-8): The final stretch focused on polishing the main menu, adding the supplied image assets, improving the game-over popup, and checking the basic play flow. Some smaller issues remained, such as touch movement state, scoring clarity, and unused references from older UI elements, but the core game was playable by the end of the sprint.
4. The Roadblocks
Roadblocks: The biggest roadblock was translating a detailed game design into a clean, finished game within one day. The AI could generate the structure quickly, but tuning the gameplay and UI took more iteration than expected. Some parts of the handoff were implemented well, like the menu, collectibles, and boss chase, while other details became messy, especially scoring behavior and leftover code from removed screens.
Another roadblock was visual consistency. A game needs to feel polished, not just function correctly. Even though the project uses supplied assets and a cartoon office theme, making every popup, HUD item, button, and gameplay object feel like one unified game required extra adjustment.
5. Key Takeaways
What worked best was the speed of the AI-assisted build. The project went from a markdown plan to a playable browser game very quickly, with no frameworks or build tools required.
What worked worst was the handoff precision. Some requirements were interpreted loosely, and a few outdated references stayed in the code after features changed. This showed that AI can move fast, but it still needs careful review and testing.
My final thought: If I had one more day, I would clean up the scoring system, improve mobile touch controls, remove stale code, and do more playtesting on different screen sizes. If I could redo this project, I would make the handoff document shorter and more strict, focusing only on the must-have gameplay and UI rules so fewer details get lost during implementation.