authoring-adept-loopslisted

# Composing a loop with adept A loop is a system that prompts agents so a human doesn't have to: each turn it **discovers** work, **hands off** to an agent, **verifies** the result, **persists** state, and **reschedules**. Skip any move and the loop fails a predictable way — no verification is an agent nodding at itself; no persistence starts from scratch every morning; no schedule is a script someone forgets to run. adept manages two of the six parts as canonical, synced resources — **skills** (discovery knowledge) and **agents** (the generator/evaluator pair). The rest (worktrees, connectors, memory files, schedules) belong to the harness and repo; this skill tells you how to wire them together. ## Scaffold the composition ```bash adept loop add ci-triage --workflow ``` creates: - `skills/ci-triage/` — discovery skill (triage template: Read → Judge → Write → Hand off → Stop). `activation: manual` on purpose: the *automation* invokes it by name; it must not auto-fire in normal sessions. - `agents/ci-triage-reviewer.md` — evaluator agent (adversarial template: assume broken, act don't read, PASS/REJECT verdict). - `.github/workflows/adept-loop-ci-triage.yml` — cloud cron skeleton (only with `--workflow`); fill in the harness invocation + auth secret. Then edit the scaffolds, `adept agent check ci-triage-reviewer`, `adept sync`. ## The five moves, mapped | Move | Where it lives | adept's part | |---|---|---| | Discovery | triage **skill** — what to read, how t