Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for game designers

Platform Certification Checklist Agent

A build with every platform requirement tested and passing, with evidence ready for the submission

Quality controlComplianceCreativesIT and developmentProduct development
See how it worksGet access
Platform Certification Checklist Agent: what goes in, what the agent does and what you get

What it does

A console or store submission is rejected because the game does not handle a suspended state or a disconnected controller, and the team loses three weeks. This agent works through the platform's technical requirements before submission. It reads the requirements document and the build's behaviors, turns each requirement into a test, such as save during suspend, error on a network drop or a controller removed, and runs them against the build or lists the manual tests for the team. It records pass or fail with evidence. After the developer fixes failures, it retests them and any related requirements, looping until the list is clean. It also checks required metadata, ratings and store assets. The producer approves submission. Edge case: a requirement that applies only to online features is marked not applicable if the game has none.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueYes, continueApprovedNoNo 1 STARTS WHEN Submission planned 2 USES A TOOL Read the platform requirements document 3 DOES Turn each requirement into a test or manual check 4 USES A TOOL Run the tests on the build or list the manual checksfor the team 5 DOES Record pass, fail or not applicable with evidence 6 CHECKS THE RESULT Do all requirements pass or have an approved notapplicable reason? If not: List failures with evidence and assign them todevelopers. Back to step 3. 7 DOES Wait for fixes and rebuild 8 USES A TOOL Retest the failed and related requirements 9 CHECKS THE RESULT Do the retested requirements now pass withoutbreaking others? If not: Reopen the requirement and repeat the test onthe new build. Back to step 8. 10 YOU APPROVE Producer approves submission 11 RESULT Certification report and submission package
Read the steps as a list
  1. Submission planned
  2. Read the platform requirements document
  3. Turn each requirement into a test or manual check
  4. Run the tests on the build or list the manual checks for the team
  5. Record pass, fail or not applicable with evidence
  6. Do all requirements pass or have an approved not applicable reason?If not: List failures with evidence and assign them to developers. Back to step 3.
  7. Wait for fixes and rebuild
  8. Retest the failed and related requirements
  9. Do the retested requirements now pass without breaking others?If not: Reopen the requirement and repeat the test on the new build. Back to step 8.
  10. Producer approves submissionThe agent waits here for your OK.
  11. Certification report and submission package

How it decides

A requirement passes only with recorded evidence from a test. Not applicable needs a stated reason from the producer.

  • A requirement passes only with recorded evidence
  • Retest related requirements when a fix touches shared code
  • Mark a requirement not applicable only with the producer's reason
  • Stop submission if any mandatory requirement fails

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Platform and requirement version
  • Test devices available
  • Requirements marked not applicable
  • Evidence format
  • Who approves submission

What keeps you in control

It always asks you first

  • Producer approves the final submission

Hard limits

  • Never submit a build itself
  • Never mark a failed requirement as passed

It stops when

  • Done: All mandatory requirements pass with evidence
  • Stop: A requirement cannot be tested with the available devices, so the agent lists it for manual testing

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensThe agent maps 148 requirements to tests. Three fail: save data is lost on suspend, no message appears on network drop, and a controller removal stalls the game. After fixes it retests: the suspend save passes, but the controller fix breaks a pause menu requirement. It reopens that item. A third build passes all 148, and the producer approves submission.

More agents for game designers

Quality control · Creatives

Level Layout Playability Review Agent

A level with no unreachable areas or unplanned spikes, ready for playtest

10 steps2 checks2 jobs
Quality control · Creatives

Build Smoke Test Gatekeeper Agent

A build that has passed the smoke path or a clear report on what broke and why

10 steps2 checks4 jobs
Monitoring · Reporting

Store Page and Review Monitor Agent

A weekly view of what players say, linked to tickets, with replies ready for approval

10 steps2 checks2 jobs
Quality control · Creatives

Accessibility Option Audit Agent

A tested accessibility checklist and an honest statement of what the game supports

10 steps2 checks4 jobs