Notion Knowledge Capture

1---
2name: notion-knowledge-capture
3description: Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
4metadata:
5  short-description: Capture conversations into structured Notion pages
6---
7 
8# Knowledge Capture
9 
10Convert conversations and notes into structured, linkable Notion pages for easy reuse.
11 
12## Quick start
131) Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.
142) Identify the right database/template in `reference/` (team wiki, how-to, FAQ, decision log, learning, documentation).
153) Pull any prior context from Notion with `Notion:notion-search` → `Notion:notion-fetch` (existing pages to update/link).
164) Draft the page with `Notion:notion-create-pages` using the database’s schema; include summary, context, source links, and tags/owners.
175) Link from hub pages and related records; update status/owners with `Notion:notion-update-page` as the source evolves.
18 
19## Workflow
20### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
211. Add the Notion MCP:
22   - `codex mcp add notion --url https://mcp.notion.com/mcp`
232. Enable remote MCP client:
24   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
253. Log in with OAuth:
26   - `codex mcp login notion`
27 
28After 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.
29 
30### 1) Define the capture
31- Ask purpose, audience, freshness, and whether this is new or an update.
32- Determine content type: decision, how-to, FAQ, concept/wiki entry, learning/note, documentation page.
33 
34### 2) Locate destination
35- Pick the correct database using `reference/*-database.md` guides; confirm required properties (title, tags, owner, status, date, relations).
36- If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki/documentation DB.
37 
38### 3) Extract and structure
39- Extract facts, decisions, actions, and rationale from the conversation.
40- For decisions, record alternatives, rationale, and outcomes.
41- For how-tos/docs, capture steps, pre-reqs, links to assets/code, and edge cases.
42- For FAQs, phrase as Q&A with concise answers and links to deeper docs.
43 
44### 4) Create/update in Notion
45- Use `Notion:notion-create-pages` with the correct `data_source_id`; set properties (title, tags, owner, status, dates, relations).
46- Use templates in `reference/` to structure content (section headers, checklists).
47- If updating an existing page, fetch then edit via `Notion:notion-update-page`.
48 
49### 5) Link and surface
50- Add relations/backlinks to hub pages, related specs/docs, and teams.
51- Add a short summary/changelog for future readers.
52- If follow-up tasks exist, create tasks in the relevant database and link them.
53 
54## References and examples
55- `reference/` — database schemas and templates (e.g., `team-wiki-database.md`, `how-to-guide-database.md`, `faq-database.md`, `decision-log-database.md`, `documentation-database.md`, `learning-database.md`, `database-best-practices.md`).
56- `examples/` — capture patterns in practice (e.g., `decision-capture.md`, `how-to-guide.md`, `conversation-to-faq.md`).
57