operating-loop-workflow
The operating-loop-workflow skill installs a seven-move multi-agent orchestration workflow from the AgentOps plugin into the user's local Claude workflows directory, then executes it with a specified capability or intent. Use this skill to bootstrap and run the operating loop (shape, plan, pre-flight, implement, capture phases) for AgentOps plugin users managing multi-agent systems, with optional plan-only mode for safe validation before implementation.
git clone --depth 1 https://github.com/boshu2/agentops /tmp/operating-loop-workflow && cp -r /tmp/operating-loop-workflow/images/gemini/skills/operating-loop-workflow ~/.claude/skills/operating-loop-workflowSKILL.md
# /operating-loop-workflow
> **One job:** Make the `operating-loop` multi-agent Workflow available to this install, then run it.
**YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.**
The seven-move operating loop (shape → plan → pre-flight → implement → capture) ships as a
Claude Code **Workflow-tool** script at `.claude/workflows/operating-loop.js`. Claude Code
plugins do **not** auto-load `.claude/workflows/` from an install — workflows resolve only from
the project cwd or `~/.claude/workflows/`. So this skill installs the bundled script into the
user workflows directory, then invokes it.
## Steps — run in order
1. **Install the workflow (idempotent — only copies when the bundled script is newer or missing):**
```bash
mkdir -p "$HOME/.claude/workflows"
src="${CLAUDE_PLUGIN_ROOT}/.claude/workflows/operating-loop.js"
dst="$HOME/.claude/workflows/operating-loop.js"
if [ -f "$src" ] && { [ ! -f "$dst" ] || [ "$src" -nt "$dst" ]; }; then
cp "$src" "$dst" && echo "installed operating-loop workflow -> $dst"
else
echo "operating-loop workflow already current (or bundle not found)"
fi
```
2. **Run it** via the Workflow tool, passing the user's capability/intent as `args`:
- Full loop: `Workflow({ name: "operating-loop", args: "<the capability/intent to drive through the loop>" })`
- Plan-only (the safe Shape → Plan → Pre-flight half, no implementation):
`Workflow({ name: "operating-loop", args: { mode: "plan", intent: "<intent>" } })`
3. **Report** the returned `intent`, `plan`, pre-flight `verdicts`, and `closeout` to the user.
## Notes
- After step 1 succeeds once, the workflow is invocable directly via the Workflow tool (`Workflow({name:'operating-loop'})`) in future sessions — this skill is the installer + first-run entry point.
- The script is a leaf Workflow (it does not nest other workflows). Source of truth: `.claude/workflows/operating-loop.js`.
- Re-running step 1 is safe and cheap; it copies only when the bundled script is newer.Switch a caller-selected coding-agent Triggers: "switch account", "rotate coding-agent account".
Use when operating ACFS flywheel health checks, init, and agent loop tooling from ~/acfs/bin/acfs.
Use Agent Mail as an optional messaging and Triggers: "coordinate writers", "reserve files".
Operate explicit orchestrator, implementer Triggers: "agent-native factory", "role-shaped agent panes", "persistent workers".
Run AGY headlessly via scheduled ticks or `agy -p`, capture agentapi JSONL evidence, and validate automated AGY loops or event streams.
|-
Use an explicitly selected AGY runtime for Triggers: "agy", "antigravity", "AGY evidence".
|-