| 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
- Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.
- Identify the right database/template in
reference/ (team wiki, how-to, FAQ, decision log, learning, documentation).
- Pull any prior context from Notion with the available search tool → page-read tool (existing pages to update/link).
- Draft the page with the available Notion create tool using the database schema; include summary, context, source links, and tags/owners.
- Link from hub pages and related records; update status/owners with the available Notion update tool as the source evolves.
Workflow
0) If Notion tools are unavailable, pause and ask the user to enable the Notion integration:
- Enable the
notion MCP entry in editors/agents/opencode/opencode.json for this environment or session.
- Complete the Notion auth flow if OpenCode prompts for it.
- Restart OpenCode or the current session if the tools still do not appear.
After the integration is enabled, finish your answer and tell the user to retry so 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 the available Notion create tool with the correct data-source identifier; 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 the available Notion update tool.
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.
References and examples
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).examples/ — capture patterns in practice (e.g., decision-capture.md, how-to-guide.md, conversation-to-faq.md).
