What problem does it solve? When working on a game product across many phases (brief, game loop, architecture, implementation), it is easy to lose track of where the product stands, which phase comes next, and what inputs are missing. This Skill reads the process registry and the current status file, then tells you exactly what to do next without forcing any workflow on you. ## Core Features & Use Cases - Phase positioning: Scans docs/product/ and the active delivery slice to determine which phases are done, approved, or missing, and names the next phase with its required inputs. - Producer-reviewer gate management: Routes review verdicts (approved, rework, blocked) to the right skill, enforces a maximum of 2 reviews per artifact, and classifies blockers into self-fixable (Class A) versus owner-escalation (Class B). - Status file hygiene: Keeps .process/status.md synchronized with actual artifacts immediately after every event, including a checkpoint verification before reporting readiness to the owner. - Use Case: You return to a game project after a two-week break and cannot remember whether the story map was approved. Invoke this Skill to rescan the repository, reconcile the checklist, and get a concrete next step such as running the handoff-spec phase. ## Quick Start Ask the orchestrator to check where my game product currently stands in the process and tell me what to do next.
