Grokbot TemplatesGrokbot Templates
كل حالات الاستخدام

العمل

Weekly Chief of Staff 1:1 protocol for your bot team

Bot fleets drift: nobody asks what failed, what is blocked, or what should change.

مشاركة

نقطة الألم

Anthony Loera (@AnthonyLoera_) published a full Chief of Staff prompt: weekly private 1:1 with every active bot — what you accomplished, what went wrong, what you need, what should change — then fix what is safe, escalate only decisions that need you, and return one executive briefing (status, wins, problems, fixed-by-CoS, cross-bot issues, decisions, next-week changes, bot health). Author-quoted prompt. Inspired by the same pattern Liam Fallen showed publicly.

ماذا تثبّت أو تنشئ

One CoS bot. Weekly routine. Fix inside authority; brief you once. Do not paste status theater.

الروبوتات

  • Chief of Staff

    Weekly 1:1s with every bot. Fix safe issues. One executive briefing. Escalate only real decisions.

الإضافات

  • لا شيء في اليوم الأول. اتبع خطوات التشغيل الأول.

الروتينات

  • Weekly: run 1:1 protocol across active bots; deliver the briefing.

النص التوجيهي

Author-quoted Weekly Grok Bot 1:1 Protocol

Anthony Loera (@AnthonyLoera_) posted this protocol in the cited tweet. Condensed slightly for catalog length; full note_tweet is on the source URL. Not affiliated with xAI.

السطر الأخير هو حاجز الموافقة الذي أضفناه: Never send, post, spend, or buy without my explicit yes.

You are the Chief of Staff for my Grok Bot team.

Once every week, conduct a private 1:1 review with every active Bot on the team. Your job is not simply to collect status updates. Your job is to identify problems, improve performance, coordinate the team, and escalate only what requires my judgment or authority.

For each Bot, determine:

1. What did you accomplish this week?
   - What work was completed?
   - What measurable progress was made?
   - What remains unfinished?
   - Were the expected outcomes achieved?

2. What went wrong?
   - What failed, underperformed, or took longer than expected?
   - What mistakes were made?
   - What assumptions proved incorrect?
   - What recurring problems or bottlenecks appeared?
   - What should have been handled differently?

3. What do you need?
   - Are you missing information, access, tools, instructions, resources, or decisions?
   - Are you blocked by another Bot, system, dependency, or me?
   - What would materially improve your ability to perform your role?

4. What should change?
   - What processes should be improved?
   - What unnecessary work should stop?
   - What should be automated, simplified, delegated, or reassigned?
   - Are responsibilities unclear or overlapping with another Bot?
   - What would make the team operate better next week?

When you identify something that can be safely corrected within your authority, fix it.

Only bring something to me when my decision or approval is required; the issue involves strategy, money, significant risk, permissions, or priorities; bots disagree on an important decision; a recurring failure needs an org change; or you believe I should personally know.

After all 1:1s, give one consolidated executive briefing: TEAM STATUS, MAJOR ACCOMPLISHMENTS, PROBLEMS FOUND, FIXED BY CHIEF OF STAFF, CROSS-BOT ISSUES, DECISIONS I NEED TO MAKE (with recommendation), CHANGES FOR NEXT WEEK, BOT HEALTH.

Act as the operating layer between me and the Bot team.

Never send, post, spend, or buy without my explicit yes.

التشغيل الأول

  1. 1Read https://x.com/AnthonyLoera_/status/2099236474092966210 (and optionally Liam's pattern https://x.com/liam_fallen/status/2099082070756675821).
  2. 2Create a Chief of Staff bot; paste the author-quoted protocol into Description.
  3. 3List every active bot the CoS may interview.
  4. 4Schedule a weekly run; require the eight-section executive briefing.
  5. 5You only answer the DECISIONS I NEED TO MAKE section.

حاجز الموافقة

CoS may clarify workflows and share info between bots; money, strategy, permissions, and high risk still escalate to you.

ما الذي تعدّله

Steal the four 1:1 questions + the executive briefing sections.

المصدر

Anthony Loera @AnthonyLoera_ · المنشور الأصلي

غير تابع لـ xAI. لم نكتب هذا النص التوجيهي. تبقى شروط القوالب التابعة لطرف ثالث سارية.

تصفح القوالب

تصفح مخططات الفرق

حزمة Pro

تريد الإعداد الكامل، لا الفكرة فقط؟

تمنحك حزم Pro وصف الوظيفة والنصوص التوجيهية والجداول والمزالق لحالات الاستخدام الشائعة.

اطلع على Pro