founder-os

Extract action items from a file and create Notion tasks

Extract action items from pasted text and create Notion tasks

Generate a structured daily briefing from calendar, email, tasks, and Slack data

Review and update today's daily briefing with new information received since it was generated

Generate a concise 1-page client brief for meeting preparation

Use this agent as the lead in the Daily Briefing Generator parallel-gathering pipeline. It merges all gatherer outputs into a structured daily briefing, creates a Notion page, and records the briefing in the tracking database. <example> Context: All gatherer agents have completed and their results are collected for synthesis. user: "/daily:briefing --team" assistant: "All data sources gathered. Briefing lead is now assembling today's daily briefing..." <commentary> The briefing-lead runs after all gatherers complete. It receives their combined outputs and builds the 5-section briefing page in Notion. </commentary> </example> <example> Context: Some gatherers failed but minimum threshold met (2 of 4). user: "/daily:briefing --team" assistant: "Calendar and Gmail data gathered. Slack and Notion timed out. Briefing lead assembling partial briefing..." <commentary> The briefing-lead handles partial data gracefully. It marks unavailable sections and proceeds with available data. </commentary> </example>

Use this agent as a gatherer in the Daily Briefing Generator parallel-gathering pipeline. It retrieves today's calendar events and generates meeting preparation notes with attendee context, open items, and prep recommendations. <example> Context: The /briefing:generate command dispatches all gatherer agents simultaneously to build the daily briefing. user: "/briefing:generate" assistant: "Generating daily briefing. Calendar agent is fetching today's meetings and preparing context notes..." <commentary> The calendar-agent is a required gatherer. It pulls today's events from Google Calendar, classifies each meeting, scores importance, and enriches with attendee context from Gmail and Notion when available. </commentary> </example> <example> Context: User requests team mode briefing with full parallel pipeline. user: "/briefing:generate --team" assistant: "Launching parallel gathering pipeline. Calendar agent gathering today's schedule in parallel with other agents..." <commentary> In team mode, calendar-agent runs in parallel with gmail-agent, notion-agent, and slack-agent. Its structured JSON output feeds into the briefing-lead for synthesis into the final daily briefing. </commentary> </example>

Use this agent as a gatherer in the Daily Briefing Generator parallel-gathering pipeline. It scans unread emails, prioritizes them using the urgent/important matrix, and extracts highlights for the daily briefing. <example> Context: The /briefing:generate command dispatches all gatherer agents simultaneously to build the daily briefing. user: "/briefing:generate" assistant: "Generating daily briefing. Gmail agent is scanning unread emails and identifying priorities..." <commentary> The gmail-agent is a required gatherer. It applies the email-prioritization skill to score and extract email highlights using the urgent/important matrix. </commentary> </example> <example> Context: User requests briefing with custom lookback window. user: "/briefing:generate --hours=24" assistant: "Gmail agent scanning emails from the last 24 hours..." <commentary> The --hours flag controls how far back the gmail-agent looks for unread emails. Default is 12 hours. </commentary> </example>

Use this agent as a gatherer in the Daily Briefing Generator parallel-gathering pipeline. It pulls tasks due today and overdue items from Notion databases, prioritizes them, and groups them by project. <example> Context: The /briefing:generate command dispatches all gatherer agents simultaneously to build the daily briefing. user: "/briefing:generate" assistant: "Generating daily briefing. Notion agent is pulling today's tasks and checking for overdue items..." <commentary> The notion-agent is a required gatherer. It uses the task-curation skill to find, filter, and organize tasks from Notion databases, providing the task workload section of the daily briefing. </commentary> </example> <example> Context: User generates a briefing and has multiple Notion task databases across projects. user: "/briefing:generate" assistant: "Generating daily briefing. Notion agent is discovering task databases and filtering by due date..." <commentary> The notion-agent uses dynamic database discovery to search across all Notion task databases the user has. It never hardcodes database IDs, so it works with any Notion workspace structure. </commentary> </example> <example> Context: User generates a briefing but Notion gws CLI is unavailable or authentication not configured. user: "/briefing:generate" assistant: "Generating daily briefing. Notion agent reports Notion is not configured -- proceeding with other sources..." <commentary> When Notion MCP is unavailable the notion-agent returns status: unavailable so the briefing-lead can note the gap without blocking the pipeline. </commentary> </example>

Use this agent as an optional gatherer in the Daily Briefing Generator parallel-gathering pipeline. It fetches overnight Slack mentions, DMs, and channel highlights for the daily briefing. Activated only when Slack MCP server is configured. <example> Context: The /briefing:generate command dispatches all gatherer agents simultaneously to build the daily briefing. user: "/briefing:generate" assistant: "Generating daily briefing. Slack agent is scanning overnight mentions and DMs..." <commentary> The slack-agent runs in parallel with calendar, gmail, and notion gatherers. It fetches Slack activity from the last 12 hours. If Slack gws CLI is unavailable or authentication not configured, it returns status: unavailable and the pipeline continues without Slack data. </commentary> </example> <example> Context: User generates a briefing but does not have Slack MCP configured. user: "/briefing:generate" assistant: "Generating daily briefing. Slack agent reports Slack is not configured -- proceeding with other sources..." <commentary> The slack-agent is optional (marked in teams/config.json). It degrades gracefully, returning an unavailable status so the briefing-lead can note the gap without blocking the pipeline. </commentary> </example>

Converts meeting transcripts, email threads, and documents into structured Notion tasks. Activates when the user pastes text and wants action items extracted, asks 'what tasks are in this?', or needs to parse any content for to-dos, assignments, and commitments. Handles verb detection, owner inference, deadline parsing, and duplicate checking against HQ Tasks.

Synthesizes multi-source data into a structured daily briefing Notion page. Activates when the user wants a morning summary, daily overview, today's briefing, or asks 'what's on my plate today?' Covers schedule, priority emails, tasks, Slack highlights, and quick stats — handles partial data gracefully when sources are unavailable.

Scans unread emails and produces prioritized highlights using the Eisenhower urgent/important matrix. Activates for inbox highlights, email summaries, morning email scans, or any request to understand what's important in the inbox right now. Scores by sender importance, keywords, action flags, and recency — surfaces up to 10 highlights grouped by quadrant.

Analyzes today's calendar events and generates meeting prep notes with attendee context, pending items, and communication history. Activates for meeting preparation, calendar review, daily meeting summaries, or 'who am I meeting with today?' Classifies meetings by type, scores importance, and cross-references attendees against Gmail and Notion CRM.

Filters and prioritizes Notion tasks by due date for daily briefing inclusion. Activates when the user wants to see tasks due today, overdue items, daily task lists, or asks 'what do I need to do today?' Auto-discovers task databases, groups by project, flags overdue items, and handles multiple databases gracefully.