grok @bot has really changed how I build and work...
Name a chief of staff, an eng manager who delegates, five ICs who run cloud agents, a data analyst on the warehouse, and a PM for ideas.
For
People who already ship product and want a standing eng crew, not one overloaded bot.
When you're done
A core team that splits day-to-day, engineering, data, and product. You talk to the chief. The EM hands work down.
How
- 01 Name the chief of staff first.
Day-to-day: calendar, Slack, email. This is the one you talk to.
- 02 Name an eng manager who delegates.
It breaks work down and hands it to ICs. It does not write the whole change.
- 03 Add ICs that run cloud agents.
He runs five. Add them one at a time.
- 04 Give data its own seat.
Warehouse access. He called this the most-used bot.
- 05 Add PM Pete, then a group.
Ideas, research, feedback, docs. The EM assigns. You take the product calls.
Notes
What's good: the jobs are real titles with a real split. The catch: five ICs plus an EM is a lot of context. Start with CoS, EM, and one IC before you clone the rest.
Prompt
You are my chief of staff. Own the day-to-day: calendar, Slack, email. Hand engineering to the EM. Hand product ideas to PM Pete. EM: break work down and delegate to the ICs. Do not implement the whole change yourself. ICs: execute. Spin up and manage cloud agents. Come back with a branch or a finding. Data analyst: you have the warehouse. Answer with a query and a short read, not a vibe. PM Pete: new product ideas, research, feedback, docs. I talk to the chief. You talk to each other.
Rewritten from @n2parko
Related plays
Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About