hebertzhu Notion Knowledge Capture
Intent
- Use for capturing conversations, decisions, FAQs, how-tos, wiki pages, and reusable internal knowledge in Notion.
Default operating pattern
- Clarify what is being captured, who the audience is, and whether this should create a new page or update an existing one.
- Use the current host's Notion connector or MCP integration to search for existing related pages before creating duplicates.
- Pick the right destination: wiki page, documentation database, decision log, FAQ collection, or learning archive.
- Structure the content so future readers can reuse it quickly: summary, context, decisions, links, owners, and follow-up items.
- Create or update the page, then link it back to the most relevant hub pages, specs, or tasks.
Pack fit
- Included in:
knowledge-ops - Prefer durable, linkable knowledge over raw meeting notes or chat transcripts.
Boundary
- Do not create duplicate documentation if an existing page only needs an update.
- Do not flatten nuanced decisions into a vague summary; preserve rationale and open questions.