email-ops-run

Run Email Ops

This is a convenience entrypoint that runs the whole system via the plugin agent email-ops-operator.

Usage

Run one of:

• /email-ops-run morning
• /email-ops-run cleanup
• /email-ops-run retro
• /email-ops-run voice-refresh

Optional flags (space-separated):

• shadow forces shadow mode behavior (no archive/trash/drafts; propose + digest + log only)
• live-archive allows auto-archive if config permits (never enables trash)
• no-labels avoids applying labels (digest only)

Examples:

• /email-ops-run morning shadow
• /email-ops-run cleanup live-archive

Dispatch Rules

1. Parse $ARGUMENTS.
2. If the first token is missing or unrecognized, ask a single clarifying question and stop.
3. Prefer delegating the work to the email-ops-operator agent with a concise mode-specific instruction.
   • If your environment does not support agent delegation, run the same instructions yourself, following the email-ops-operator spec.
   • morning: run the morning triage loop and produce the daily digest
   • cleanup: run the light cleanup pass only (no drafts)
   • retro: run the weekly retrospective using the audit log schema
   • voice-refresh: run the optional monthly voice refresh behavior (sent mail only; no raw bodies stored)
4. Enforce global non-negotiables:
   • never auto-send
   • never auto-spam
   • destructive actions remain gated by policies/threshold-config.yaml
5. Artifact outputs:
   • always: digest + summary in the current thread
   • include a CSV audit-log block if a shared sheet is not available

Mode-Specific Prompts

When delegating, send exactly one of these to email-ops-operator:

morning

Run morning triage. Apply deterministic hygiene first, then classify remaining items. Follow policies/threshold-config.yaml and policies/always-human-rules.md. Produce a digest and include unsubscribe recommendations (recommend-only).

cleanup

Run light cleanup only. Scope to obvious low-value broadcast content. No drafts. Never touch protected tiers or high-risk threads. Prefer label-only if any doubt.

retro

Run weekly retrospective for the last 7 days. Measure precision/rescues and propose updates. Separate safe auto-applied updates vs approval-required. Do not lower destructive thresholds without explicit operator approval.

voice-refresh

Run a voice refresh on sent mail only (last 30 days). Produce distilled updates to voice-profile.md, relationship-rules.md, and do-not-say.md guidance. Do not store raw email bodies anywhere outside the mailbox.