For example, my work on schema, my protobufs/flatbuffers language replacement for multiplayer games, parallelizes very nicely across 15 languages on the sprint system. https://github.com/mas-bandwidth/schema.
See roadmap here: https://github.com/mas-bandwidth/schema/blob/main/ROADMAP.md
Very difficult to coordinate this amount of work in || without some sort of structured work system.
Even more AI coding work here if you are curious: https://patreon.com/masbandwidth
I did some prototype games, one thing that worked really well for me was having a deterministic replay system where the agents could drive the gamestate via recorded inputs. Kept me from having to do any playtesting or debugging in the main agentic loop.
https://github.com/mas-bandwidth/fixed3d -- port of box3d to fixed point :)
https://github.com/mas-bandwidth/fixed -- fixed point math library
I do you think now need to watch out for the opposite problem. These things become so easy to build that the temptation is just to go ahead and build. But unless you really do need them, all that new code just goes to waste. The cost to produce has become very low, but sometimes the value can end up being negative.