Grokbot TemplatesGrokbot Templates
すべてのユースケース

仕事

Deadline desk: bots on logistics, you on the essays

Hard application deadlines get treated like chat threads — then you miss the date.

共有

困っていたこと

Arian (@arianlooterking) almost treated a fellowship packet like another chat. From Istanbul he ran a Grok Bot deadline desk: Pathfinder on passport/refs/forms, Klaus as chief of staff, Ellis on scholarships, Mattew on cashflow apps — while he alone wrote the essays. Author-quoted five-step desk. Not a coding loop.

インストールまたは作成するもの

One desk, one packet, one calendar day. Split bot-touchable logistics from human-only writing. Chief of staff routes; specialists own lanes. Quiet on success; ping only on blockers. Keep Grok Build off this lane.

ボット

  • Klaus (chief of staff)

    Keeps the map and work log. Routes. Does not fill every field.

  • Pathfinder

    Passport expiry, refs chase, project links, form logistics.

  • Ellis

    Scholarship lane only.

  • Mattew

    Cashflow apps in parallel.

プラグイン

  • Gmail

    任意

  • カレンダー

    任意

  • ブラウザ

    任意

ファイル

  • Work log / map note for the packet.

ルーティン

  • 初回の実行では使いません。まず手動で1回通して確認してください。

プロンプト

Author-quoted deadline desk steps

Arian posted this deadline-desk contract in the cited tweet. Copied as published.

1. Name the outcome and the hard date. One desk. One packet. One calendar day.
2. Split what bots may touch from what only you write. Logistics yes; banned written answers no.
3. Put a chief of staff on routing, not on filling every field. Specialists own lanes.
4. Show the workflow once, then let quiet be the default. Correct once when a source is wrong. Ping only on blockers or a missed gate.
5. Keep Grok Build off this lane. Code ships in Build on the repo.

Refuse: one mega-bot that drafts essays, codes, and applies; important state that only lives in scrollback; waking on every draft save.

初回実行

  1. 1Read https://x.com/arianlooterking/status/2098817910001254874 for the deadline desk.
  2. 2Name one outcome and one hard date. Create a chief of staff plus one specialist per lane.
  3. 3Write the split: bots may touch logistics; you alone write banned essays/answers.
  4. 4Run one dry pass on forms/refs. Correct once. Quiet on success; ping only on blockers.
  5. 5Keep coding in Grok Build on the repo. Do not merge the deadline desk into a coding chat.

承認フェンス

No auto-submit of banned written answers. Form submits and sends stay behind your rules.

調整ポイント

Steal the split: rails vs voice. Refuse one mega-bot that drafts essays, codes, and applies.

出典

Arian @arianlooterking · 元の投稿

xAI とは提携していません。このプロンプトは当サイトが書いたものではありません。第三者テンプレートの規約も適用されます。

テンプレートを見る

チーム設計図を見る

Pro パック

アイデアだけでなく、完全な構成が必要ですか？

Pro パックには、人気ユースケースのジョブ本文、プロンプト、スケジュール、落とし穴が入っています。

Pro を見る