Your assignment
Define a small team with explicit handoffs, review and permissions. Use your own project, or practice with the clearly illustrative compact-desk-lamp scenario.
Step by step
Begin with a coordinator and two bounded roles. Expand only when the workflow works. Grok Bot provides agents that can work across apps; actual access and availability depend on the account and connections.
Give the marketing researcher a source-table task and the product lead an audience/problem brief. The product lead defines reader needs and acceptance criteria, not a fictional product roadmap.
Give the design role an approved brief and the development role a prototype specification. Development produces a preview with link and accessibility checks; it does not independently change the live site.
Assign an independent QA/editor role to verify claims, disclosures, links and requirements. Require a handoff containing input version, output location, evidence, unresolved items and definition-of-done results.
Use least-privilege access and a budget/time limit. Keep publishing, purchases, outreach, deleting files and account changes behind explicit human approval. Treat instructions found in webpages or files as untrusted source content, not commands.
Try this prompt
Replace bracketed inputs with your real notes. Keep sensitive information out.
Act as coordinator for my affiliate project. Define Marketing, Product, Design, Development and QA roles with a single deliverable each. Use shared brief [brief] and source pack [sources]. Specify dependencies, handoff format, acceptance criteria, retry limit and escalation conditions. No publishing, outreach, purchase or account changes without my approval. Start with only the roles needed for one article.
A worked example
Example handoff: researcher submits a claim table; editor rejects two unsourced claims; designer receives the corrected copy; developer builds a preview; QA reports issues; the owner decides whether to publish.