{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.mature-roster-five-moves","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.mature-roster-five-moves","name":"Five moves for a roster that already exists","category":"onboarding","problem":"The gap for an established roster is almost never more Bots.","technique":"In 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_works":"A 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_use":"Any roster with a chief and specialists already running.","manual_ref":"E","evidence":"documented","related":["pat.save-the-method-as-a-skill","pat.state-on-disk","pat.audit-routines-across-bots","pat.report-your-inputs","pat.steal-a-published-pack"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}