morning-brieflisted

## Why this exists, and what I'd change **Why it exists.** Two PMs at the same company often miss the same news because nobody runs the daily scan. This automates it: industry news plus email summary plus today's calendar, delivered to a Slack DM in 60 seconds. Cuts the "what did I miss?" ritual. **Design tradeoffs.** - **Slack DM delivery instead of email.** Lower-friction for daily checking. Cost: needs Slack MCP wired. Emails are more universal across orgs that don't use Slack. - **Fixed 6am local schedule via GitHub Action.** Reliable across machines, no local cron to maintain. Cost: ties you to GitHub Actions usage limits. On a long-haul timezone shift, it fires at the wrong local time until you update the schedule. - **Industry news topics are static config.** You declare topics once and the scout runs them daily. Cost: if your focus shifts mid-quarter, the brief is still scanning yesterday's beats. **What I'd change.** Replace the fixed schedule with "send 30 minutes before your first calendar meeting." That hits the right cognitive moment regardless of timezone or meeting density. --- # Morning Brief Deliver a 60-second daily brief covering industry news, email highlights, and today's schedule, straight to your Slack DMs. ``` /morning-brief → run now, send to Slack /morning-brief draft → run now, save to file only (no Slack) /morning-brief schedule → show automation status ``` **Time:** ~30 seconds. Uses Gmail MCP, Notion MCP, Slack MCP, and