### 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) Define the capture
Ask purpose, audience, freshness, and whether this is new or an update.
Determine content type: decision, how-to, FAQ, concept/wiki entry, learning/note, documentation page.
### 2) Locate destination
Pick the correct database using `reference/*-database.md` guides; confirm required properties (title, tags, owner, status, date, relations).
If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki/documentation DB.
### 3) Extract and structure
Extract facts, decisions, actions, and rationale from the conversation.
For decisions, record alternatives, rationale, and outcomes.
For how-tos/docs, capture steps, pre-reqs, links to assets/code, and edge cases.
For FAQs, phrase as Q&A with concise answers and links to deeper docs.
### 4) Create/update in Notion
Use `Notion:notion-create-pages` with the correct `data_source_id`; set properties (title, tags, owner, status, dates, relations).
Use templates in `reference/` to structure content (section headers, checklists).
If updating an existing page, fetch then edit via `Notion:notion-update-page`.
### 5) Link and surface
Add relations/backlinks to hub pages, related specs/docs, and teams.
Add a short summary/changelog for future readers.
If follow-up tasks exist, create tasks in the relevant database and link them.
SynapticSkills