/loop-engineering
Loop engineering runtime Grill + Monitor
$ npx -y skills add alvinunreal/oh-my-opencode-slim --skill loop-engineering --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/loop-engineering
Context preview
The summary Claude sees to decide when to auto-load this skill.
Loop engineering runtime Grill + Monitor
SKILL.md
loop-engineering.SKILL.mdname: loop-engineering
description: Loop engineering runtime Grill + Monitor
Loop Engineering Skill
Grill (orchestrator interview)
1. Goal: "What are you trying to accomplish?" 2. Success criteria: "Describe how we know the loop succeeded." 3. Success type: choose from `test`, `build`, `lint`, `command`, `fileExists`, `oracle`, `observer`, `manual`. For CLI steps provide `successCommand`; for file detection provide `successPath`. 4. Execute agent: fixer / designer / explorer / librarian 5. Verify agent: oracle / observer / test 6. Max attempts (default 3) 7. Optional context files: which files or directories should be read before execution?
Loop Monitor
- 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
Notes
- 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.
Read more
name: loop-engineering description: Loop engineering runtime Grill + Monitor
Loop Engineering Skill
Grill (orchestrator interview)
1. Goal: "What are you trying to accomplish?" 2. Success criteria: "Describe how we know the loop succeeded." 3. Success type: choose from `test`, `build`, `lint`, `command`, `fileExists`, `oracle`, `observer`, `manual`. For CLI steps provide `successCommand`; for file detection provide `successPath`. 4. Execute agent: fixer / designer / explorer / librarian 5. Verify agent: oracle / observer / test 6. Max attempts (default 3) 7. Optional context files: which files or directories should be read before execution?
Loop Monitor
- 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
Notes
- 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.
Lean, fine tuned Opencode multi agent suite · Mix any models · Auto delegate tasks
Repo: alvinunreal/oh-my-opencode-slim
Other skills on oh-my-opencode-slim.
- /clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library
Open skill - /codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping
Open skill - /deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
Open skill - /oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
Open skill - /reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
Open skill - /simplify
Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.
Open skill