[01] LOOP
IntegrationsintervalHardenedTemplate

The AIOps Agent for ML on Autopilot

Inspired by Chamber — The AIOps Agent for ML Teams. Loop until the workflow is current, exceptions are owned, and human sign-off is captured where required.

Inspired by Chamber

by Trooper

Kickoff prompt
/loop 30m Start the "The AIOps Agent for ML on Autopilot" loop.

Inspired by Chamber (https://www.usechamber.io).

Goal: open work triaged, exceptions owned, and core integrations workflow current with audit trail
Max iterations: 20
Between iterations run: Report open queue items, stale tasks, failed automations, and items awaiting human approval for Chamber
Exit when: zero open items without owner or explicit escalation, all external actions approved or sent, and systems of record current

Step 1 — Ingest telemetry: Aggregate logs, metrics, traces, and agent events across the stack.
Step 2 — Detect anomalies: Correlate alerts and drift; rank by customer impact and blast radius.
Step 3 — Triage incidents: Assign owners, gather context, and propose remediation paths.
Step 4 — Remediate and verify: Apply fixes or runbooks; confirm recovery before closing.
Step 5 — Postmortem and harden: Document root cause, add guards, and update monitors.

## Before you start

Connect plugins:
- GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs.
- Support tickets (required) — Read customer tickets, feedback, onboarding gaps, and support themes.
- CRM (required) — Read accounts, deals, owners, stages, and onboarding state.
- Linear / Jira (required) — Read roadmap, task, bug, owner, and status context.

Attach skills:
- Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition.
- Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped.
- CI debugging (optional) — Read failing checks, logs, and the smallest actionable root cause.
- Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial.
- Customer operations (optional) — Identify at-risk accounts, missing setup steps, and safe next actions.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.

Steps

1. Ingest telemetry

Aggregate logs, metrics, traces, and agent events across the stack.

2. Detect anomalies

Correlate alerts and drift; rank by customer impact and blast radius.

3. Triage incidents

Assign owners, gather context, and propose remediation paths.

4. Remediate and verify

Apply fixes or runbooks; confirm recovery before closing.

5. Postmortem and harden

Document root cause, add guards, and update monitors.

Flow diagram

Guardrails

Rules the agent must follow so it cannot cheat the exit condition.

  • Require human approval before customer-facing sends, payments, or legal submissions unless pre-approved templates apply
  • Preserve full audit trail linking source data to every automated action
  • Escalate compliance, safety, or regulatory-sensitive items immediately

More Integrations loops