Aurora — Spec: Slack Notifications
Overview
Aurora's Slack notification feature delivers personal alerts to team members when an action item is assigned to them, as extracted from a meeting recording. This is one of the three core MVP features defined in the project kickoff brief. Aurora — Kickoff Brief.md
See the Project Overview for the full project context, and Audio-to-Events Pipeline for how action items are first extracted before notifications are triggered.
Requirements
| # | Requirement | Priority | Notes |
|---|---|---|---|
| SN-1 | Send a Slack notification to a user when an action item is assigned to them | Must-have | Core MVP scope Aurora — Kickoff Brief.md |
| SN-2 | Notifications must be personal (sent to the assigned user only) | Must-have | Do not send notifications for every event; only for assigned action items Planning Meeting 2026-06-09.md |
| SN-3 | Action items originate from auto-extraction of meeting recordings | Must-have | Depends on Audio-to-Events Pipeline Aurora — Kickoff Brief.md |
Out of Scope (MVP)
The following are explicitly excluded from the MVP: Aurora — Kickoff Brief.md
- Mobile push notifications
- Recurring-event reminders via Slack
- External calendar sync notifications (e.g., Google Calendar, Outlook)
- Notifications for all events (only action item assignments trigger notifications) Planning Meeting 2026-06-09.md
User Flow
Behavior
- Notifications are triggered per action item assigned to a user, not for every event recorded. Planning Meeting 2026-06-09.md
- The notification is targeted at the individual user assigned to that specific action item.
- The notification channel is Slack; no other notification channels are in scope for MVP.
- The trigger point is the completion of the Audio-to-Events Pipeline for a given recording.
Edge Cases
⚠️ The source document does not specify edge case handling. The items below are structural placeholders derived from the defined scope — all marked low confidence.
- Unrecognized assignee: If the extracted action item cannot be matched to a known Slack user, behavior is unspecified. Aurora — Kickoff Brief.md
- Duplicate notifications: If the same recording is re-processed, deduplication logic is not defined in the brief. Aurora — Kickoff Brief.md
- No Slack account: Handling for team members without a linked Slack account is not addressed in scope. Aurora — Kickoff Brief.md
Dependencies & Related Pages
| Dependency | Type | Page |
|---|---|---|
| Audio-to-Events Pipeline | Upstream (data source) | Spec: Audio-to-Events Pipeline |
| Shared Team Calendar | Sibling feature | Spec: Shared Team Calendar |
| Action Items tracker | Output consumer | Action Items |
| Project overview & milestones | Context | Project Overview |
Milestone
Slack notifications are part of the Calendar + Slack beta, targeted for 2026-08-15, ahead of the pilot launch on 2026-09-15. Aurora — Kickoff Brief.md
- 2026-08-15Calendar + Slack beta (includes Slack notifications)Aurora — Kickoff Brief.md
- 2026-09-15Pilot launch — 3 teamsAurora — Kickoff Brief.md
Owner
Feature delivery owned by Dev Patel (backend) under PM Mina Park, as part of the broader Aurora team. Aurora — Kickoff Brief.md