### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
1. Add the Notion MCP:
`codex mcp add notion --url https://mcp.notion.com/mcp`
2. Enable remote MCP client:
Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
3. Log in with OAuth:
`codex mcp login notion`
After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
### 1) Gather inputs
Ask for objective, desired outcomes/decisions, attendees, duration, date/time, and prior materials.
Search Notion for relevant docs, past notes, specs, and action items (`Notion:notion-search`), then fetch key pages (`Notion:notion-fetch`).
Capture blockers/risks and open questions up front.
### 2) Choose format
Status/update → status template.
Decision/approval → decision template.
Planning (sprint/project) → planning template.
Retro/feedback → retrospective template.
1:1 → one-on-one template.
Ideation → brainstorming template.
Use `reference/template-selection-guide.md` to confirm.
### 3) Build the agenda/pre-read
Start from the chosen template in `reference/` and adapt sections (context, goals, agenda, owner/time per item, decisions, risks, prep asks).
Include links to pulled Notion pages and any required pre-reading.
Assign owners for each agenda item; call out timeboxes and expected outputs.
### 4) Enrich with research
Add concise Codex research where helpful: market/industry facts, benchmarks, risks, best practices.
Keep claims cited with source links; separate fact from opinion.
### 5) Finalize and share
Add next steps and owners for follow-ups.
If tasks arise, create/link tasks in the relevant Notion database.
Update the page via `Notion:notion-update-page` when details change; keep a brief changelog if multiple edits.
SynapticSkills