loop-engineering

Loop engineering runtime Grill + Monitor

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/alvinunreal/oh-my-opencode-slim --skill loop-engineering

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name	loop-engineering
description	Loop engineering runtime Grill + Monitor

Goal: "What are you trying to accomplish?"
Success criteria: "Describe how we know the loop succeeded."
Success type: choose from test, build, lint, command, fileExists, oracle, observer, manual. For CLI steps provide successCommand; for file detection provide successPath.
Execute agent: fixer / designer / explorer / librarian
Verify agent: oracle / observer / test
Max attempts (default 3)
Optional context files: which files or directories should be read before execution?

Listen to callbacks:
- onLoopComplete(loopID, success) → report final outcome
- onEscalated(loopID, reason) → escalate to human
- onManualReview(loopID, reason) → prompt human to approve/fail and call resolveManualReview(loopID, passed, reason)
Show current state and attempt count on each callback
For manual verification, present the failure reason before asking for pass/fail
If human forces cancellation, call cancel(loopID) through the orchestrator

Manual verification is the minimal on-ramp (autoresearch pattern). It pauses the loop until resolveManualReview is called. Do not auto-resolve.
BackgroundJobBoard signals (totalErrors, timeoutCount) are already baked into the runtime.