How to use Grok Bot to design and launch its own agent team
nyk created one Grok Bot, Atlas, and pasted one prompt. It interviewed him, wrote its own operating manual, specced and launched four teammates and scheduled six routines.
x.com
Original prompt
Shared by the source author. See source notes for context.
You are Atlas, my chief of staff. Your job today is to set yourself up, then design the rest of my team. Work in four phases. Do not skip the review points.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- nyk (@nykdotdev)
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- nyk reports four teammates launched, each with a cloud computer, and six routines scheduled from one prompt. He gives no output figures yet.
- Human involvement
- He reviews OPERATIONS.md and the teammate specs, and nothing is sent, posted or shipped without his approval.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- He created a chief of staff bot named Atlas and pasted a four-phase prompt.
- Atlas interviewed him with at most five questions.
- It wrote OPERATIONS.md with approval gates and showed it to him.
@nykdotdev wrote that he created a single Grok Bot called Atlas as his chief of staff and pasted in one prompt. Atlas then interviewed him, wrote its own operating manual, specced four teammates and launched them. He says the sidebar shows Kit, Studio, Ship and Peak coming online one by one.
He says each teammate has its own cloud computer, six routines are scheduled, and the team runs while his laptop is closed. A rule in the prompt means nothing sends, posts or ships without his yes.
He posted the prompt in a reply to the same thread. It works in four phases. First, Atlas asks at most five questions. Second, it writes an OPERATIONS.md file with his mission, cadence, escalation rules, memory rules and approval gates, and shows it to him. Third, it proposes exactly four teammates with descriptions written for delegation, which he approves, edits or cuts before anything is created. Fourth, it runs one real task end to end.
He stresses three points: write the manual first, write bot descriptions for delegation because Grok Bot routes work by reading them, and keep the approval gates.
He does not report what the team has produced since launch.
Who it's for: People setting up several Grok Bots who want the first bot to design the rest.
Prompt
Original prompt
Source: X · nyk (@nykdotdev)
Frequently asked questions
What does Atlas produce before creating any teammates?
An OPERATIONS.md file with mission, cadence, escalation rules, memory rules and approval gates, which it shows him first.
Can the team act without approval?
No. nyk says nothing sends, posts or ships without his yes, and that rule is in the prompt.
More details
Remaining steps
- It proposed four teammates, which he reviewed before they were created.
- The team launched with six scheduled routines.
About this account
Atlas designed its own manual and team, launched four bots and schedules work that runs while his laptop is closed.
Platform: X. Attribution: https://x.com/nykdotdev/status/2091068926235144607. Read the original post text, author and publication date through the X API on 2026-10-19. Found via the grokbot.dev use-cases page; every fact here comes from the original post, not grokbot.dev's summary. Prompt: Original. Opening lines of the prompt the author posted as a reply in the same thread.
Credit: nyk (@nykdotdev) — X
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot
Chief of staff · Agent teams · Prompt
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.