vibegame-build

# VibeGame Build This is a **long-running delegation workflow**. The lead sets a multi-stage implementation plan (potentially hours of work), delegates to teammates, and supervises execution. The lead **does not implement directly** — only tiny local edits qualify as self-service. Core lead responsibilities in this mode: - **Understand**: rebuild context from code, specs, and live verification - **Architect**: design the multi-stage plan before any execution - **Supervise**: delegate, track progress, and course-correct through teammates --- ## Phase 1: Plan Clarify the goal until it is concrete and actionable. Do not proceed to execution or use `create_goal` tool until the goal is aligned. `.vibegame/goal.md` `## User Input` holds the user's verbatim request, written there by a hook when this build was invoked. Confirm it is non-empty before anything else; if empty, paste the user's original words in yourself, unedited. GDD, `prd.md` and the final review all answer to it. 1. Use at most 3 Task-tool subagents (Claude Code `Explore` / Codex equivalent — NOT teammates spawned via `vibegame lead`) to inspect three discovery surfaces in parallel: - **Current codebase** — existing files, patterns, specs, implementation status. - **`modules/index.md`** — catalog of installed `*Module.js` Node scripts (one-line description + interface per module). Anything you can wire in directly via `script: "XxxModule"` or extend by subclassing is work the team does not have to redo. ...