An engineering bot team with written rules: the chief of staff merges only reviewed, green PRs

Qué instalar o crear

The engineering bot plans, hands code to a coding agent, reviews the full diff against main, and keeps CI moving. The chief of staff merges only after review with every required check green, under a standing approval he gave once in writing; money math, auth and migrations are flagged before merge every time. Bug fixes start with a test that fails on main; PRs stay small; review is capped at two delta rounds, then scope narrows. Repeated mistakes go into the repo's AGENTS.md.

El prompt

Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.

Primer uso

1. 1Read https://x.com/schnieds/status/2108754367037788240 (credit @schnieds).
2. 2Give each product its own engineering bot and one chief of staff above them.
3. 3Write the playbook: failing test first, small PRs, two review rounds max.
4. 4Write the merge rule once: reviewed, all checks green, high-risk changes flagged to you.
5. 5When an agent repeats a mistake, add the fix to AGENTS.md.

Qué ajustar

Almost every improvement started as something he had to say twice; write it where the agents will read it.

Fuente

Aaron Schnieder @schnieds · Publicación original

Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.