{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.chief-builds-the-team","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.chief-builds-the-team","name":"Let the chief design the roster","category":"orchestration","problem":"Operators guess at new Bots and end up with redundant ones nobody deletes.","technique":"After a context-gathering interview, ask the chief to identify coverage gaps rather than propose ideas, and to recommend removals as well as additions. Redescribe your constraints as priorities change and let it redesign.","why_it_works":"It can see the agents you already have, so it avoids redundant suggestions and designs around your current constraint rather than a generic org chart.","when_to_use":"Roster review, and whenever priorities shift.","manual_ref":"3.13","evidence":"reported","related":["pat.chief-of-staff","pat.roster-size-ceiling"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}