# Meeting Actions

Parse action items from meeting summaries stored in the `Meeting Summaries` folder.

## Arguments
$ARGUMENTS

Arguments can be combined in any order, e.g. `/meeting-actions today`, `/meeting-actions this week`, `/meeting-actions Figma Dev Handoff`, `/meeting-actions last 3 days`

- **Timeframe keywords** — controls which files are scanned by date:
  - `today` — files from today only
  - `yesterday` — files from yesterday only
  - `this week` — files from the current Monday through today
  - `last N days` — files modified in the last N days (e.g. `last 3 days`)
  - If no timeframe is given, default to the last 7 days
- **Meeting name** — any non-timeframe text is treated as a partial filename match (case-insensitive)
- Both can be combined: `/meeting-actions Figma last 3 days`

## Instructions

### Step 1: Find the right files
The Meeting Summaries folder is at:
`/Users/aj.siegel/Projects/FullFocus/Meeting Summaries/`

Parse $ARGUMENTS to extract:
1. A timeframe (if present) — translate it to a number of days or a specific date range
2. A name filter (if present) — any remaining text after stripping timeframe keywords

Use the Bash tool to list `.md` files (excluding README.md) in the folder, filtered by:
- Modification date matching the resolved timeframe
- Filename containing the name filter (if provided)

Sort results by date descending. If no files match, say so clearly.

### Step 2: Read the summary files
Read each file. Meeting summaries may come in various formats (Zoom AI, manual notes, etc.). Look for action items in any of these forms:
- Lines starting with `- [ ]` or `* [ ]` (task checkboxes)
- Sections labeled "Action Items", "Next Steps", "Follow-ups", "To-Dos", "Decisions"
- Lines containing "AJ will", "AJ to", "@AJ", "action:", "TODO:", "follow up"
- Any sentence where AJ is the named owner of something

### Step 3: Output the actions
Present a clean, scannable list organized by meeting. For each meeting:

```
## [Meeting Name] — [Date]
- [ ] Action item 1
- [ ] Action item 2
```

After the list, ask: **"Want me to add any of these to Notion as tasks?"**
If yes, ask which ones, then for each:
- Use the Notion MCP to create a task in the Task Tracker (data source: `2c0abd6c-450a-8085-80a0-000ba136a154`)
- Set Status to "Not started"
- Infer a reasonable due date if one is mentioned in the summary, otherwise leave blank
- Ask if there's a project to link it to, or try to infer from context

### Formatting rules
- Keep action items concise — verb-first (e.g. "Send follow-up to Lucia", not "AJ will send a follow-up to Lucia")
- Flag any action items that appear time-sensitive with ⚡
- If no clear action items are found, say so and show a brief summary of the meeting instead