Stage 3 component of the WowCube pipeline, invoked by cube_orchestrator — not a standalone user entry point. Use only when the orchestrator routes to asset generation because the manifest exists but packed assets and _ids.h do not. Generates AI sprite PNGs (from each sprite's gen_prompt) and synthesised WAV sounds, pauses for user review, then packs them into `assets/packed/`, `assets/wav/`, and `src/app_<game>_ids.h`.
Use as the single entry point for ANY WowCube game work — when the user says "make a game", "design a game", "create a game", "build the game", "implement this", "start coding", "run the prompts", or wants to resume a WowCube project. ALSO the entry point for modding an existing, already-working game — when the user wants to change, tweak, reskin, or extend one ("замодить", "swap this sprite", "change the speed", "add a level"); it detects build-from-scratch vs modding and routes accordingly. The master controller for the whole pipeline: it routes through design, prompts, assets, and implementation, and manages every sub-skill and subagent.
Stage 2 component of the WowCube pipeline, invoked by cube_orchestrator — not a standalone user entry point. Use only when the orchestrator routes to prompt generation because a GDD exists but the prompts file and asset manifest do not. Decomposes a GDD into implementation prompts plus the asset manifest, where every sprite carries a ready-to-run AI generation prompt (gen_prompt).
Infrastructure-and-packaging component of the WowCube pipeline, invoked by cube_orchestrator — not a standalone user entry point. The orchestrator routes here at two points: the infra gate before Stage 4 (scaffold app_<game> from the template, pack art, and smoke-build + launch the simulator) and Stage 5 after implementation (build the ARM device target and verify the cube-loadable .oct embeds the code). Use only when the orchestrator routes here.
Stage 1 component of the WowCube pipeline, invoked by cube_orchestrator — not a standalone user entry point. Use only when the orchestrator routes to game design because no GDD exists yet. Produces a non-technical Game Design Document from a game idea via a discovery interview.
Use when verifying WowCube game code after a coder agent completes implementation. Contains two agent roles: Requirements Agent (checks completeness, GDD, regressions) and Template Agent (checks code against app_ai_template.h). The orchestrator deploys each agent separately.