Digest

1---2name: digest3description: Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.4argument-hint: "[--daily | --weekly | --since <date>]"5---6 7# Digest Command8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Scan recent activity across all connected sources and generate a structured digest highlighting what matters.12 13## Instructions14 15### 1. Parse Flags16 17Determine the time window from the user's input:18 19- `--daily` — Last 24 hours (default if no flag specified)20- `--weekly` — Last 7 days21 22The user may also specify a custom range:23- `--since yesterday`24- `--since Monday`25- `--since 2025-01-20`26 27### 2. Check Available Sources28 29Identify which MCP sources are connected (same approach as the search command):30 31- **~~chat** — channels, DMs, mentions32- **~~email** — inbox, sent, threads33- **~~cloud storage** — recently modified docs shared with user34- **~~project tracker** — tasks assigned, completed, commented on35- **~~CRM** — opportunity updates, account activity36- **~~knowledge base** — recently updated wiki pages37 38If no sources are connected, guide the user:39```40To generate a digest, you'll need at least one source connected.41Check your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools.42```43 44### 3. Gather Activity from Each Source45 46**~~chat:**47- Search for messages mentioning the user (`to:me`)48- Check channels the user is in for recent activity49- Look for threads the user participated in50- Identify new messages in key channels51 52**~~email:**53- Search recent inbox messages54- Identify threads with new replies55- Flag emails with action items or questions directed at the user56 57**~~cloud storage:**58- Find documents recently modified or shared with the user59- Note new comments on docs the user owns or collaborates on60 61**~~project tracker:**62- Tasks assigned to the user (new or updated)63- Tasks completed by others that the user follows64- Comments on tasks the user is involved with65 66**~~CRM:**67- Opportunity stage changes68- New activities logged on accounts the user owns69- Updated contacts or accounts70 71**~~knowledge base:**72- Recently updated documents in relevant collections73- New documents created in watched areas74 75### 4. Identify Key Items76 77From all gathered activity, extract and categorize:78 79**Action Items:**80- Direct requests made to the user ("Can you...", "Please...", "@user")81- Tasks assigned or due soon82- Questions awaiting the user's response83- Review requests84 85**Decisions:**86- Conclusions reached in threads or emails87- Approvals or rejections88- Policy or direction changes89 90**Mentions:**91- Times the user was mentioned or referenced92- Discussions about the user's projects or areas93 94**Updates:**95- Status changes on projects the user follows96- Document updates in the user's domain97- Completed items the user was waiting on98 99### 5. Group by Topic100 101Organize the digest by topic, project, or theme rather than by source. Merge related activity across sources:102 103```104## Project Aurora105- ~~chat: Design review thread concluded — team chose Option B (#design, Tuesday)106- ~~email: Sarah sent updated spec incorporating feedback (Wednesday)107- ~~cloud storage: "Aurora API Spec v3" updated by Sarah (Wednesday)108- ~~project tracker: 3 tasks moved to In Progress, 2 completed109 110## Budget Planning111- ~~email: Finance team requesting Q2 projections by Friday112- ~~chat: Todd shared template in #finance (Monday)113- ~~cloud storage: "Q2 Budget Template" shared with you (Monday)114```115 116### 6. Format the Digest117 118Structure the output clearly:119 120```121# [Daily/Weekly] Digest — [Date or Date Range]122 123Sources scanned: ~~chat, ~~email, ~~cloud storage, [others]124 125## Action Items (X items)126- [ ] [Action item 1] — from [person], [source] ([date])127- [ ] [Action item 2] — from [person], [source] ([date])128 129## Decisions Made130- [Decision 1] — [context] ([source], [date])131- [Decision 2] — [context] ([source], [date])132 133## [Topic/Project Group 1]134[Activity summary with source attribution]135 136## [Topic/Project Group 2]137[Activity summary with source attribution]138 139## Mentions140- [Mention context] — [source] ([date])141 142## Documents Updated143- [Doc name] — [who modified, what changed] ([date])144```145 146### 7. Handle Unavailable Sources147 148If any source fails or is unreachable:149```150Note: Could not reach [source name] for this digest.151The following sources were included: [list of successful sources].152```153 154Do not let one failed source prevent the digest from being generated. Produce the best digest possible from available sources.155 156### 8. Summary Stats157 158End with a quick summary:159```160---161[X] action items · [Y] decisions · [Z] mentions · [W] doc updates162Across [N] sources · Covering [time range]163```164 165## Notes166 167- Default to `--daily` if no flag is specified168- Group by topic/project, not by source — users care about what happened, not where it happened169- Action items should always be listed first — they are the most actionable part of a digest170- Deduplicate cross-source activity (same decision in ~~chat and email = one entry)171- For weekly digests, prioritize significance over completeness — highlight what matters, skip noise172- If the user has a memory system (CLAUDE.md), use it to decode people names and project references173- Include enough context in each item that the user can decide whether to dig deeper without clicking through