ProblemThe gap for an established roster is almost never more Bots.
TechniqueIn order: save working tasks as skills and then routines, move board and project state into /workspace files, watch the weekly meter and run the routine audit, add the outer-loop rule and the silent-failure guard, and steal a published pack rather than authoring the next specialist.
Why it worksA mature roster is more likely than a new one to carry a long orchestrator thread and a historical inbox, which is exactly the shape of the best-documented blow-up.
When to useAny roster with a chief and specialists already running.