I vibe coded a mobile game in 8 working days. The decision log was the real product.
说明与用途
作者在8个工作日内使用AI代理和详细的决策日志构建了一款移动游戏。流程包括澄清目标、头脑风暴、制定规范、拆分任务、专家评审和逐步实现。396条决策日志成为项目核心和未来重建的指南。
问题
Developing a mobile game with AI agents while ensuring quality, reproducibility, and maintainability, without relying on human code authorship for every decision.
结果
The workflow produced a fully functional mobile game in 8 working days, with a comprehensive decision log that became the core of the project brief, enabling future rebuilds and tutorials.
工作流
- Clarify the rough idea and ask the agent to restate the goal, list assumptions and unknowns, and ask questions until nothing is ambiguous.
- Brainstorm several approaches for each open question.
- Spec the result into a spec with acceptance criteria.
- Cut the spec into small tickets that are buildable, testable and mergeable on their own.
- Have specialist agents (architect, security engineer, product manager) review the spec and tickets before any code exists.
- Implement one ticket, run a code review, commit, and move on to the next.
证据
The repository holds the whole process, not just the code: the original rough idea, four rewrites of it, the spec, 48 tickets, every prompt in order (workflow.md), and a log of 396 decisions.
The workflow is described in full in CodingAgentOrchestration. In short: Clarify, Brainstorm, Spec, Tickets, Review, Build.
Every non‑obvious choice gets a numbered entry with three parts: the question, the decision, and what it costs.
After 391 decisions I asked the agent to rewrite the idea document with every decision folded into it, and the war stories turned into general rules.
- 记录日期: 2026-10-13T16:41:19.207Z