[01] LOOP
OperationsintervalHardened

Morning Operator Brief

Daily interval loop that reads your calendar, open tickets, and inbox priorities, then delivers a concise operator brief with ranked actions.

by Trooper

Kickoff prompt
/loop 1d Start the "Morning Operator Brief" loop.

Goal: morning brief delivered with ranked priorities and blockers surfaced
Max iterations: 1
Between iterations run: Verify brief covers calendar, tickets, and top three priorities
Exit when: brief is delivered with calendar conflicts, ticket status, and ranked actions

Step 1 — Monitor: Read calendar, open tickets, and priority inbox.
Step 2 — Act: Draft time-blocked plan and prep tasks.
Step 3 — Surface: Deliver ranked priorities, conflicts, and blockers.

## Before you start

Connect plugins:
- Google Calendar (required) — Read upcoming meetings, attendees, and scheduling context.
- Slack (required) — Post summaries, approvals, blockers, and handoff updates.
- Notion (required) — Read and update approved briefs, docs, calendars, and reports.
- Gmail (required) — Read incoming mail and prepare safe draft replies for approval.
- 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.
- Operations briefing (optional) — Summarize sources into concise, owner-aware, non-invented updates.
- 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. Monitor

Scan calendar for today's meetings, open tickets by severity, and unread priority mail.

2. Act

Draft time-blocked plan, pre-write standup notes, and queue safe prep tasks.

3. Surface

Deliver a concise brief: top three priorities, conflicts, blockers, and what can wait.

Flow diagram

Guardrails

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

  • Do not send external messages without approval
  • Cite ticket IDs and meeting times — do not invent calendar events
  • Flag blockers and overdue items explicitly

More Operations loops