Agent Handles Emails End-to-End
story: Agent Handles Emails End-to-End
Role
Admin (Lucas, with Marcus via relay)
Key
agent-handles-emails
Want
As an admin, I want to tell the email agent what I need ("send contract reminders", "send monthly fee notice", "send tournament announcement") and have it handle composition, testing, approval gating, and delivery end-to-end
So That
So that I never re-build email infrastructure per email type and every send goes through the standard nuclear gate, regardless of who triggers it
Acceptance Criteria
- [ ] Agent at
~/westside-email-agent/recognizes natural-language send intents ("send contract reminders" / "send monthly fees" / etc.) - [ ] Agent picks the right query + layout from existing infrastructure, or stops and surfaces the gap (missing query / missing EmailType / missing layout) if any piece is missing
- [ ] Agent runs sop-email-send 8-step workflow on every send, no shortcuts
- [ ] Test email always sent first to
draneylucas@gmail.combefore any real recipient - [ ] Approval gates honored: standard single-approval for non-contract, contract enhanced gate (triple confirm) for contract-related sends
- [ ] EmailLog row exists for every recipient after blast; agent reports delta vs intended audience
- [ ] Zero unapproved sends across all runs
Success Metric
Lucas (or Marcus via relay) can send any email type whose audience query + layout exist with one CLI session, zero code changes, and zero unapproved sends.
Related Architecture
- arch-email — system architecture (components, layouts, flow)
Related
- project-westside-email-agent — parent project
- board-westside-email-agent — execution board
- sop-email-send — the universal workflow agent follows
- feedback_email_blast_nuclear_gate — gate provenance