LegalOS Ops on Autopilot

/loop 30m Start the "LegalOS Ops on Autopilot" loop.

Inspired by LegalOS (https://www.legalos.ai).

Goal: open work triaged, exceptions owned, and core documents 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 LegalOS
Exit when: zero open items without owner or explicit escalation, all external actions approved or sent, and systems of record current

Step 1 — Intake matters: Collect new matters, client documents, and deadlines for LegalOS workflows.
Step 2 — Extract requirements: Parse facts, jurisdictions, and deliverables from intake with confidence scores.
Step 3 — Draft work product: Generate drafts, filings, or responses grounded in firm templates and precedent.
Step 4 — Human review: Route judgment calls and final outputs to attorney sign-off before delivery.
Step 5 — Close and track: File completed work, update matter status, and surface follow-ups.

## Before you start

Connect plugins:
- GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs.

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.

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.