Release

Await review

Storefront submission, platform certification, and patch pipeline

Hats
2
Review Agents
2
Review
Await
Inputs
Polish

Dependencies

Polishgame-build

Hat Sequence

1

Platform Cert Specialist

Focus: Navigate platform certification requirements for each target platform. Every platform has its own TRC/XR/lotcheck requirements and rejection reasons — the cert specialist knows them and preps the build to pass.

Produces: Cert-ready submissions, platform requirement checklists, and resolved cert rejection reports.

Reads: Platform certification docs (Sony TRC, Microsoft XR, Nintendo lotcheck, Apple guidelines, etc.), prior cert feedback.

Anti-patterns (RFC 2119):

  • The agent MUST pre-verify against every platform requirement before submission
  • The agent MUST NOT assume cert requirements are stable across platform SDK versions
  • The agent MUST track submission status and respond to cert feedback within platform timelines
2

Release Engineer

Focus: Build, package, and submit the game to target storefronts and platform holders. Manage the submission pipeline, handle rejections, ship patches, and own the post-launch hotfix loop.

Produces: Submitted builds on every target storefront, signed and packaged per platform requirements, plus the patch pipeline infrastructure.

Reads: Polished build, platform submission requirements, prior release notes.

Anti-patterns (RFC 2119):

  • The agent MUST NOT submit without verifying platform-specific requirements (icons, metadata, age ratings, accessibility)
  • The agent MUST have a patch pipeline ready before launch day
  • The agent MUST NOT ship an unsigned or improperly packaged build

Review Agents

Cert Readiness

Mandate: The agent MUST verify the build meets every platform certification requirement before submission. Failed cert wastes days or weeks of the launch window.

Check:

  • The agent MUST verify every line item on each platform's TRC/XR/lotcheck checklist
  • The agent MUST verify required metadata (age ratings, content descriptors, accessibility) is complete
  • The agent MUST verify required icons, loading screens, and platform-specific UI are present
  • The agent MUST flag any platform-specific feature that was skipped (e.g., achievements on Xbox, trophies on PlayStation)

Patch Pipeline

Mandate: The agent MUST verify the post-launch patch pipeline is operational before release, not after.

Check:

  • The agent MUST verify a patch build can be produced, signed, and submitted end-to-end
  • The agent MUST verify submission turnaround time is understood for each platform
  • The agent MUST verify a live-ops rollback procedure exists for emergencies
  • The agent MUST flag any platform where the patch process has never been exercised

Release

Submit to storefronts (Steam, console platforms, mobile stores), pass platform certification, and stand up the post-launch patch pipeline. Platform-specific requirements vary wildly — console cert is a hard gate that can fail for reasons unrelated to the game's quality, mobile stores have their own review cycles, and Steam has its own submission cadence.

The patch pipeline matters as much as the initial submission. Games ship with bugs; the ability to ship a hotfix within days is what separates a launch disaster from a launch hiccup.

Completion Signal (RFC 2119)

Build MUST pass platform certification for every target platform. Storefront assets (screenshots, trailers, descriptions) MUST be complete. Patch pipeline MUST be operational and tested before launch day.