Give each game a clear home
Keep a short project brief with the core player activity, the visual direction and the next playable milestone. Link the references and decisions that matter to the current work.
BerryBlox is designed around a shared game context. The final software navigation and supported integrations will be documented for the released version.
Give each assignment one outcome
Split design, code, worlds, interfaces and assets into work you can review. Name the result, the relevant constraints and the way you will test it.
Every plan includes fifteen specialist agents. Your plan controls how many may work at once; more concurrent agents do not remove task dependencies or the need for review.
Keep useful work and its context
Save accepted files alongside the brief, source references and any licensing or compatibility limits. A preview image helps you judge appearance; the editable source is what lets you revise the work.
For website account features, your saved briefs belong in Briefs. Software access and billing have their own account pages so a saved idea is not confused with an active software session.
Review before expanding
Finish a small playable slice, inspect its actual result and test it before repeating a pattern across the whole game. Keep unresolved questions visible instead of treating queued work as complete.
The website describes this workflow; it does not itself execute agent assignments or connect to Roblox Studio.