Ingeniería
One QA bot per app, woken by Basecamp cards in "QA Needed"
QA is the bottleneck between "done" and "ready for review".
Qué dolía
Scott Reyes (@scottdreyes) has a QA bot for each of his three software applications. In one day they QA'd 27 cards over 43 rounds and left 65 notes. Not affiliated with xAI.
Qué instalar o crear
Each bot gets the QA manual (including training videos), Basecamp access and logins to the software. When a card lands in QA Needed, it wakes up, does experiential QA in the browser and code-level QA in the terminal, then moves passing cards to Ready for Human Review and failed or blocked cards back to In Progress.
Bots
QA bot (one per app)
Tests cards in QA Needed and moves them on.
Plugins
Navegador
Obligatorio
GitHub
Opcional
Rutinas
Ninguna en el primer uso. Mira primero una pasada manual.
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
- 1Read https://x.com/scottdreyes/status/2108292028853518531 (credit @scottdreyes).
- 2Write or collect your QA manual and give it to one bot per app.
- 3Give it Basecamp (or your board) access and test logins.
- 4Tell it: when a card lands in QA Needed, test in the browser and terminal, leave notes.
- 5Passing cards go to Ready for Human Review; failed or blocked go back to In Progress.
Valla de aprobación
Give the bots test logins, not admin accounts. Nothing ships until a human reviews the card.
Qué ajustar
Bots move cards between columns; a human still does the final review.
Fuente
Scott Reyes @scottdreyes · Publicación original
Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.
Paquete Pro
¿Quieres la configuración completa, no solo la idea?
Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.