Grok Bot × team discovery: agree on handoffs before creating roles
- For
- Operations
- Apps
- Grok Bot · Feishu
- Risk
- Low · read-only or writes to your own docs
- Runs
- On demand
- Level
- Intermediate
Clarify platforms, collection rules and output locations, then validate a sample across research, selection, writing and review.
The source uses reverse interviewing to define where work happens, how it is done and where results go. The questions and task sheet here are independently written.
Execution and takeover boundaries
The actions below require the agreed inputs, accounts and scope. Configuring a Routine does not expand that authorization.
Can run automatically
Collect constraints, source rules and handoff fields, compare small plans and prepare file handoffs from one sample.
Requires confirmation
Confirm role creation, delegation or contact with other Bots, platform connections, output sharing and scheduled tasks.
Take over after a failure
Stop at handoffs missing sources, owners or state transitions for user correction. Resume from the failed sample without letting later roles invent sources.
Scenario and input
Section titled “Scenario and input”Synthetic request: review ten public sources weekly, choose three topics and prepare one draft for manual publication.
1. Interview for constraints
Section titled “1. Interview for constraints”Ask about audience, platforms, time budget, sources, storage and human decisions, resolving one gap at a time.
2. Define collection rules
Section titled “2. Define collection rules”Specify keywords, time windows, identity keys and reading scope. Record unavailable data without bypassing platform restrictions.
3. Agree on three handoffs
Section titled “3. Agree on three handoffs”Define fields, owners and states for each handoff. Drafting uses approved topics and does not invent source material.
4. Compare small roster options
Section titled “4. Compare small roster options”Compare one Bot, two roles and a staged team by maintenance and waiting costs, then choose the smallest workable plan.
5. Validate one sample
Section titled “5. Validate one sample”Walk one source through selection, drafting and fact review, checking the evidence chain before creating roles or schedules.
A synthetic acceptance fixture
Section titled “A synthetic acceptance fixture”Three handoffs: sources.csv for evidence, topics.csv for review, and drafts/ for approved topics. A topic without approval_id stays pending.
Copyable task brief
Section titled “Copyable task brief”Use the synthetic fixture to prepare the deliverable for Grok Bot × team discovery: agree on handoffs before creating roles. Do not connect real services yet.Input: Synthetic request: review ten public sources weekly, choose three topics and prepare one draft for manual publication.Requirements:1. Ask about audience, platforms, time budget, sources, storage and human decisions, resolving one gap at a time.2. Specify keywords, time windows, identity keys and reading scope. Record unavailable data without bypassing platform restrictions.3. Define fields, owners and states for each handoff. Drafting uses approved topics and does not invent source material.4. Compare one Bot, two roles and a staged team by maintenance and waiting costs, then choose the smallest workable plan.5. Walk one source through selection, drafting and fact review, checking the evidence chain before creating roles or schedules.Return itemized records, evidence locations, unknowns and next steps, marking unperformed actions explicitly.Do not install tools, change access, purchase, publish, create Bots or schedule work in this pass.Acceptance and review
Section titled “Acceptance and review”A draft traces to read evidence and an explicit approval, without invented sources or automatic publication.
Review the artifacts without taking external actions.Acceptance: A draft traces to read evidence and an explicit approval, without invented sources or automatic publication.Separate pass, fail, untested and evidence; distinguish synthetic fixtures from live results.Stop on missing sources, permissions or uncertain outcomes and list the required evidence.Propose one next step with a recovery plan and wait for confirmation.Sources and applicability
Section titled “Sources and applicability”Original article: @xilo2991; published 2026-10-12.
Index-to-source mapping: strong content match.
The collector reports viewing 18 images; 0 videos remain unwatched. Images confirm source-to-topic-to-draft handoffs and human review. Two interview prompts were not obtained from the images; this guide writes its own questions.
Prices, interfaces and menus change. Check unresolved conditions against the actual account and current official documentation.
See the rewrite and verification map for all 24 sources
Verification record
Section titled “Verification record”Content updated: · Editing a page does not reverify its sources or live workflow.
Documentation review: Historical review record ·
Preserves this page’s existing source-review record. Its source notes state actual text, image, video or code coverage and unavailable material. This integration did not recheck external sources or establish a live workflow pass.
Live workflow verification: Unverified
This site has not executed the live accounts, bridges, external writes or scheduled workflow. Author demonstrations, synthetic fixtures and page checkboxes do not establish this site’s live verification.
This page is based on the sources below, last checked on . If the interface looks different, send feedback or edit the page.Send feedbackEdit this page
217 related external resources →Official sources and original authors’ posts, each with a note on what was checked.