notion-knowledge-capture

--- name: notion-knowledge-capture description: Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking. metadata: short-description: Capture conversations into structured Notion pages --- # Knowledge Capture Convert conversations and notes into structured, linkable Notion pages for easy reuse. ## Quick start 1) Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience. 2) Identify the right database/template in `reference/` (team wiki, how-to, FAQ, decision log, learning, documentation). 3) Pull any prior context from Notion with `Notion:notion-search` → `Notion:notion-fetch` (existing pages to update/link). 4) Draft the page with `Notion:notion-create-pages` using the database’s schema; include summary, context, source links, and tags/owners. 5) Link from hub pages and related records; update status/owners with `Notion:notion-update-page` as the source evolves. ## Workflow ### 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 [... prompt truncated for preview ...]