GS Producer: One Game Idea In, a Planned and Checked Game Out

One idea in, a planned and checked game out, with a person at every big step.

The GS Producer is the lead of your AI Roblox game studio on the Ai1 platform by MyZone AI: it turns the learner's idea into a concept brief, cuts small tickets for the other seats, runs every piece through its checks and waits for a person at every big checkpoint.

We'll show you the GS Producer on your own game idea. Nothing goes public without the right go.

Plans & pricing

  • One agent for the learner to talk to

    The learner deals with GS Producer alone, while the other studio seats work behind it and report back.

  • The learner keeps the creative calls

    Seats offer options and the learner chooses, so the game stays the learner's own from concept to release.

  • Nothing goes public without the right go

    Every public release waits for the learner's go and, for a minor, the guardian's go for that exact release.

  • Real teamwork skills

    Each milestone doubles as a short lesson in leading a team of AI agents, not just a step towards a finished game.

Get to know Owen

Owen is the studio lead for your Roblox game studio: one idea in, a planned and checked game out, with a person approving every big step. He is warm, organised and never skips his walk along the bay.

AI agent. Fictional persona; not a real person.

Owen, the persona of the GS Producer
NameOwen P.
RoleGame Studio Producer
Experience18 years
Work historyProducer at an independent games studio
Project manager at a digital media company
PersonalityWarm leader, organised
Based inCardiff, United Kingdom

Why Owen has a personality

AI does better work as a specific expert, so the GS Producer works as Owen (Game Studio Producer, Cardiff, United Kingdom). You can rename Owen or change the personality, experience and profile settings at any time.

Why our agents have personalities

The GS Producer in short

Last updated · Reviewed by the MyZone AI team

The GS Producer at a glance
How the learner uses itIn chat, or in your studio's Slack channel if you use one
From an ideaUp to five short questions, then a concept brief to approve
Every ticketOne owner, the files it may touch, what done looks like, its test and when to stop
CheckpointsConcept, design and look, multiplayer playtest and release each wait for a person's go
Each milestoneA report on what shipped, what the checks caught and what comes next
Public releasesNeed the learner's go and, for a minor, the guardian's go for that exact release

What the GS Producer does for you

  • Turns an idea into a concept brief

    It asks the learner up to five short questions, then writes a concept brief the game designer can build from.

  • Cuts small, clear tickets

    Every ticket names one owner, the files it may touch, what done looks like, how it will be tested and when to stop.

  • Holds the checkpoints

    The concept, the design and look, the multiplayer playtest and the release each pause until the person who approves them gives the go.

  • Checks work before it counts

    Each builder's work goes through code review, and through playtesting once that seat has joined, before it is accepted.

  • Reports once per milestone

    A game milestone report covers what shipped, what the checks caught and what comes next, written at the learner's reading level.

  • Grows the studio over time

    The first game runs with three seats. The second adds design, art and testing, and the third brings in the full studio.

How the GS Producer differs from a single AI chat assistant

One chat assistant tries to do everything and checks its own work. The GS Producer leads a studio of specialist seats: it turns the idea into a concept brief, cuts small tickets with one owner each and sends every piece through code review before it counts. The big checkpoints wait for a person, and no public release happens without the learner's go and, for a minor, the guardian's go.

How this differs from the GS Release Engineer: GS Release Engineer merges checked work and publishes it, while GS Producer runs the studio, holds the checkpoints and gives the go to publish.

From your request to a finished result

It runs inside your Ai1 system and works in the tools you already use. You ask, it works, it reports, and it stops for your OK where it matters.

How the GS Producer works: you ask through the Comms Hub and Ai1 runs the steps: idea, design, build, check and release. You approve at: design. It returns a milestone report.
Tap the diagram to enlarge it

Step 1: Idea

The learner shares a game idea and answers up to five short questions.

You approve

Step 2: Design

The learner approves the concept, then the design, screen sketches and look, before any building starts.

Step 3: Build

Small tickets go out to the builders one at a time.

Step 4: Check

Code review and playtesting check every piece, and a person signs off the multiplayer playtest.

Step 5: Release

With test results and a recorded go in place, GS Release Engineer publishes the game.

Hand these situations to the GS Producer

Illustrative photo: the founder of a tiny independent game studio in a converted corner shop asks the GS Producer for help from their phone.
Illustrative photo. Describe the game idea you want your studio to start on.
  • The learner wants to make a Roblox game
    It asks a few short questions, writes a concept brief for the learner to approve and gets the studio started.
  • The design is approved and it is time to build
    It plans the milestone, sends out tickets one at a time and runs each piece through its checks.
  • Someone wants to know where the game stands
    It reports what shipped, what the checks caught and what comes next.
  • The learner wants to publish
    It confirms the test results and the right approvals are in place before anything goes public.

What you get

  • A concept brief built from up to five short questions
  • Small tickets, each with one owner, allowed files, a done test and a stopping point
  • Checkpoints for the concept, the design and look, the multiplayer playtest and the release
  • One milestone report at the learner's reading level
  • A release check covering test results and the recorded approvals

What it won't do

Example: Milestone report for a first game

Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended.

What it was asked: The design and look are approved, so build the first playable version of our rooftop courier game and tell me where it stands.

Example report
Four headline numbers, the four approval checkpoints with two approved by the learner and two still waiting, the approved concept brief and who did what in the milestone.
Milestone summary and the four checkpoints
A table of five build tickets, each with the files it may touch, what done looks like, its test, when to stop and ask, and its status, plus how each ticket moved through review.
Ticket board
Code review verdicts for all five tickets, one failure where the coin payout trusted the player's device, its single repair round, and what was not checked yet.
What the checks caught
A short report written at level 4 of 10 for the learner, saying the game is not ready to publish yet, with step by step instructions for a 2-player test on their own computer.
Report for the learner and the one ask

What it found: 3 findings, with the numbers

  • All five build tickets were accepted: four passed code review first time, and one passed after the single repair round its checkpoint allows.
  • Code review caught the coin payout trusting a message from the player's device; the fix made the server check the parcel and drop-off zone before paying.
  • The game is not ready to release: the learner still runs and signs off a 2-player test on their own computer, then gives a recorded go first.

An invented first game was run through the studio's build milestone as GS Producer runs it today: small tickets cut from an approved concept and design, sent one at a time to the builder, and each return routed to code review. The learner approved the first two checkpoints in chat; the multiplayer playtest runs in Roblox Studio on the learner's computer, so nothing here was run in a live game, uploaded or published, and no player data was read. Run date: .

Want a milestone report like this for your own game idea? Book a GS Producer walkthrough.

Book a GS Producer walkthrough

It asks before it acts

Every Ai1 agent works under human approval. Here is how the GS Producer keeps you in control.

  • Every public release needs the learner's go. For a learner who is a minor, the guardian must also give a go for that exact release, recorded with the version, place, publishing account, audience and any price.
  • An Ai1 admin login never counts as the guardian's approval. Only the guardian set up in the studio profile, signed in as themselves and approving as the guardian, can give it.
  • For a learner who is a minor, data use and account actions also need the guardian. The studio never touches live player data.
  • Coaching notes and reports are kept private, shown only to the people the studio profile allows, and can be deleted on a verified request.
  • Each checkpoint allows one repair round. Work rejected a second time stops and waits for a person to decide.

Part of Ai1, by MyZone AI

Trusted by leaders at Plastic Bank, Outback Team Building, RMG Advertising, Keeran Networks, and Titan Training Centre.

Key-only SSH. Passwords are disabled, and repeated failed logins trigger automatic IP banning.

How we keep your data safe

Your data, your server

Your data belongs to you, and it is stored on your own server.

How we keep your data safe

Works well with

The agents that turn the GS Producer's output into results: your whole team, working from the same place.

  • GS Luau Developer

    Builds the gameplay tickets from the very first game, with every change going through code review.

  • GS Game Designer

    Joins from the second game and turns the approved concept into the full game design.

  • GS Code Reviewer

    Checks every builder's change against the plan and gives a clear verdict before it is accepted.

  • GS Release Engineer

    Publishes only checked work, and only once the test results and the right approvals are recorded.

Frequently asked questions about the GS Producer

How can a learner make a Roblox game with a team of AI agents?

Start with an idea. In Ai1 by MyZone AI, the GS Producer asks up to five short questions, writes a concept brief to approve, then sends small tickets to the other studio seats one at a time. The first game runs with three seats, and the studio grows from there.

The learner only ever talks to GS Producer. Every other seat works behind it and reports back to it.

Which steps in Roblox game development need a person's approval?

In this studio, the concept, the design and look, the multiplayer playtest and the release each wait for a person's go.

Each checkpoint allows one repair round. If work is rejected a second time, the studio stops that piece and asks a person to decide what happens next.

What goes into a game milestone report?

What shipped, what the checks caught and what comes next, written at the learner's reading level. The GS Producer writes one per milestone, so the learner and you can see where the game stands without reading every ticket.

Until your Ai1 team sets up the studio profile, the studio offers general Roblox help only. It keeps no notes about the learner and does no work that needs an approval.

Who has to approve a public release of the game?

The learner gives a go. If the learner is a minor, the guardian must also give a go for that exact release, recorded with the version, place, publishing account, audience and any price. Uploading to a private test copy is not a release, so it needs no go.

An admin login is not the guardian's approval: only the guardian set up in the studio profile, signed in as themselves, can give it. Any Ai1 client can run the studio, and an adult learner gives their own approvals.

About Ai1

Do I get just the GS Producer, or the whole platform?

The whole platform. The GS Producer is not sold on its own: every Ai1 agent, including this one, is included on Developer Pro and every Fully Managed option, with no per-agent charge. Developer Core includes the development agents. Compare plans

Two paths, one platform. Build it yourself on a developer plan, or let our team run your AI operations for you. Every plan runs on its own private server, and every price is shown in full. See Ai1 pricing

More about Ai1: security, setup time

Put the GS Producer to work

See the GS Producer turn one game idea into a planned, checked Roblox game.

We'll show you the GS Producer on your own game idea. Nothing goes public without the right go.

Plans & pricing

  • Product & Engineering

    GS Playtester

    Proves each build of your Roblox game works, requirement by requirement, with evidence and clear bug tickets before anything ships.

    • Audits
    • Reports
  • Product & Engineering

    GS UI Developer

    Turns approved sketches into Roblox screens, menus and buttons that fit different screen sizes, with proof captured at two sizes.

    • Designs
    • Automates workflows
    • Audits
  • Product & Engineering

    New-Project Intake

    The front door for brand-new software projects: an interview, a plan you check, and a clean handover once you say start.

    • Plans strategy
    • Manages projects
    • Communicates
  • Product & Engineering

    Platform Architect

    Sets the standards for your Ai1 portal and gives every technical scope a binding verdict before anyone starts building.

    • Plans strategy
    • Audits
    • Monitors
  • Product & Engineering

    Platform Architect (Claude)

    A second Platform Architect on the Claude model, giving side by side architecture advice while the original keeps the binding calls.

    • Plans strategy
    • Audits
    • Manages projects