// Create a post-meeting thank-you or follow-up email with key points and next steps. Use when user says "follow-up email", "thank you note", "post-meeting email", "send a follow-up to [person]", or after a meeting capture when next steps need communicating. See also: `draft-reply` for general email responses unrelated to a meeting.
Launch the Brain Monitor TUI, a real-time terminal dashboard for watching Claudia's memory system. Triggers on "brain monitor", "show dashboard", "memory dashboard", "terminal brain". See also: `brain` for a 3D graph view in the browser.
Launch the Brain Visualizer, a real-time 3D view of memory and relationships. Triggers on "show your brain", "visualize memory", "open the brain", "memory graph". See also: `brain-monitor` for a terminal dashboard alternative.
Process meeting notes or transcript to extract decisions, commitments, and insights. Use when user shares transcript or says "capture this meeting", "here are my notes from the call". See also: `meeting-prep` for pre-call briefings; `follow-up-draft` for post-meeting emails.
Check memory system health and troubleshoot connectivity issues. Use when memory commands aren't working, at session start if something seems wrong, or when user asks about memory status. See also: `memory-health` for the data-quality dashboard once connectivity is confirmed.
Draft an email response with tone matching the relationship context. Shows draft for approval before sending. Use when user says "draft a reply", "respond to this email", "write a response to [person]", or shares an email and asks for help replying. See also: `follow-up-draft` for post-meeting thank-yous with meeting context.
Store a document, email, or text for future reference with entity linking and provenance. See also: `ingest-sources` for multiple files; `capture-meeting` if it's meeting notes; `summarize-doc` to get a summary without filing.
| name | follow-up-draft |
| description | Create a post-meeting thank-you or follow-up email with key points and next steps. Use when user says "follow-up email", "thank you note", "post-meeting email", "send a follow-up to [person]", or after a meeting capture when next steps need communicating. See also: `draft-reply` for general email responses unrelated to a meeting. |
Draft a post-meeting follow-up or thank-you email.
/follow-up-draft [person name]
people/## Follow-Up Email: [Person Name]
### Re: [Meeting/Topic]
---
**To:** [Name] <[email if known]>
**Subject:** [Suggested subject line]
---
Hi [Name],
[Opening - thank them, reference the conversation]
[Key points or takeaways from discussion]
[Confirm any commitments - what you'll do, what they mentioned]
[Next steps or call to action]
[Warm close]
[Your name]
---
**Notes:**
- [Any context about tone or relationship]
- [Timing suggestion for sending]
**Before sending:**
- [ ] Confirm accuracy of commitments mentioned
- [ ] Check tone matches relationship
- [ ] Verify email address
---
Ready to send? Let me know if you want adjustments.
After a productive meeting:
When specific promises were made:
When more conversation needed:
After time has passed:
Based on relationship:
Based on meeting outcome:
For first-time meetings, new relationships
For meetings where they gave valuable input
For ongoing conversations
When specific commitments need clarity
I'll draft the email and show it to you. I will NOT send anything without your explicit approval.