SuperAPI AI Directory

unity-game-production

General & other

View repository

Updated 10-16 08:49

About this skill

Unity game production planning

Break game intent into an approvable, implementable, and acceptable scope; do not approve product direction, commercial capability, release method, or risk exemptions on the user's behalf.

Inputs and decisions

Read the current Work Item,docs/project-profile.yaml、docs/GDD.md and existing acceptance evidence. First eliminate factual issues from code and artifacts; when the core loop, scope, target players, acceptance, release method, or module boundaries genuinely require human trade-offs, submit to $unity-game-grilling the "facts, options and impact, recommendation, latest decision point"; do not write your own recommendation as the user's decision.

Execution and handoff

  1. Define the one-sentence experience, target players, core loop, failure/retry, minimum scope, and exclusions.
  2. Break the scope into six-phase tasks and V0-V4 scene/popup increments, each with player behavior, observable results, dependencies, resource requirements, ownership, and test points. A scene contains only its own gameplay, visuals, and persistent HUD; modal, popup, drawer, and toast each get their own independent DISPLAY_LAYER Work Item,hostSceneId which records only the runtime context. Write only the platforms selected by the user into the delivery scope.
  3. Arrange decision points only for genuine product/visual trade-offs and operations with side effects; do not create extra approval gates for ordinary local implementation.
  4. For changes, first distinguish repair、revalidate repair, revalidate, and return, return, and invalidate only the genuinely affected scope; do not rewrite other roles' documents on their behalf.
  5. Submit phase status, evidence index, and blockers to the control plane; do not directly migrate global state.

What is handed to architecture is the scope, scenes, acceptance, the set of user-approved platforms, the primary development platform, per-platform release methods, and capability switches; what is handed to gameplay, numerical, visual, and audio is the experience intent and boundaries; what is handed to QA is determinable player behavior.