Engineering
Paste one prompt: lead bot + security, performance, and QA
You become the middleman forwarding every message between specialist bots.
What hurt
@Solomonrojie publishes a stealable setup: one lead owns the plan and final package; security, performance, and QA investigate in parallel with file ownership, compact handoffs, and a hard stop after two failures. Paste the author prompt; require your OK before merge/deploy. Not affiliated with xAI.
What to install or create
Paste setup prompt → review proposed config → run investigations → you approve merge/deploy.
Bots
Lead + 3 specialists
Lead owns plan/review; security, performance, and QA investigate in parallel.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
Lead + security/performance/QA setup (author-quoted)
Quoted from @Solomonrojie — as published. Do not invent a second system prompt.
Last line is our approval fence: Never send, post, spend, or buy without my explicit yes.
Build my engineering workflow around one lead Bot and three specialists: security, performance, and QA. First inspect the repository, available tools, and existing test commands. Report missing access. Create the Bots with distinct responsibilities and put the team in a group chat so handoffs stay visible. Keep the brief and task board in a shared project folder. Give every task one owner, its dependencies, acceptance checks, and an expected output. Run independent investigations in parallel. Assign file ownership before edits and serialize changes that touch the same files. Use scripts for repeatable checks. Preserve raw logs, but pass compact results and links between Bots. Keep successful work when a step fails. Return the specific failure for correction and stop after two failed attempts. Have QA inspect the resulting patch against the brief. The lead returns the diff, test evidence, and unresolved issues. Show me the proposed configuration before applying it. Require my approval before merging, deploying, or changing production. Never send, post, spend, or buy without my explicit yes.
First run
- 1Read https://x.com/Solomonrojie/status/2114860139819798907 (credit @Solomonrojie).
- 2Paste the author-quoted lead + security/performance/QA setup prompt.
- 3Review the proposed bots, group chat, and task-board shape before applying.
- 4Let specialists investigate in parallel; lead returns diff + test evidence + unresolved issues.
- 5You press approve only when ready to merge, deploy, or change production.
Approval fence
Show config first; you approve before merging, deploying, or changing production.
What to tweak
Steal the quoted lead+3 prompt; keep merge/deploy behind your OK.
Source
Solomon Rojie @Solomonrojie · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.