otto-looplisted

# Otto Loop Skill A loop is a worker/verifier cycle: launch a worker → check verification → repeat until done or limits hit. Use for "keep trying", "babysit", or "watch this until X." For lightweight recurring checks that should return to this same conversation, prefer a cron heartbeat (`create_heartbeat`, then `delete_heartbeat` when finished). To change it, delete and recreate it. Use a loop when each iteration needs a worker/verifier lifecycle; use a schedule when each firing should create a fresh independent agent and workspace. **User's arguments:** $ARGUMENTS ## Prerequisites Read the **otto** skill. Before choosing worker or verifier providers, read `~/.otto/orchestration-preferences.json` unless the user explicitly named providers in this request. Do not start the loop until you have read it. Loops are a CLI primitive: `otto loop run`. Manage with `otto loop ls`, `otto loop inspect <id>`, `otto loop logs <id>`, `otto loop stop <id>`. ## Your job 1. Understand the user's intent from `$ARGUMENTS` and the conversation. 2. **Worker prompt** - self-contained, concrete about what to do this iteration, explicit about what counts as progress. 3. **Verification** - pick the right shape: - Shell check (`--verify-check`) for objective criteria a command can answer (`gh pr checks --fail-fast`, `npm test`). - Verifier prompt (`--verify`) for judgment ("Return done=true only if all tests pass and the changed files are coherent. Cite the command and the outcome.").