AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

notion-knowledge-capture

Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.

Original source
openai
License
MIT
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--notion-knowledge-capture at revision 49f948faa9258a0c61caceaf225e179651397431, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 13

reference/decision-log-database.md

Decision Log Database (ADR - Architecture Decision Records)

Purpose: Track important decisions with context and rationale.

Schema

| Property | Type | Options | Purpose | |----------|------|---------|---------| | Decision | title | - | What was decided | | Date | date | - | When decision was made | | Status | select | Proposed, Accepted, Superseded, Deprecated | Current decision status | | Domain | select | Architecture, Product, Business, Design, Operations | Decision category | | Impact | select | High, Medium, Low | Expected impact level | | Deciders | people | - | Who made the decision | | Stakeholders | people | - | Who's affected by decision | | Related Decisions | relation | Links to other decisions | Context and dependencies |

Usage

Create decision records with properties:
{
  "Decision": "Use PostgreSQL for Primary Database",
  "Date": "2025-10-15",
  "Status": "Accepted",
  "Domain": "Architecture",
  "Impact": "High",
  "Deciders": [tech_lead, architect],
  "Stakeholders": [eng_team]
}

Content Template

Each decision page should include:

  • Context: Why this decision was needed
  • Decision: What was decided
  • Rationale: Why this option was chosen
  • Options Considered: Alternatives and trade-offs
  • Consequences: Expected outcomes (positive and negative)
  • Implementation: How decision will be executed

Views

Recent Decisions: Sort by Date descending Active Decisions: Filter where Status = "Accepted" By Domain: Group by Domain High Impact: Filter where Impact = "High" Pending: Filter where Status = "Proposed"

Best Practices

  1. Document immediately: Record decisions when made, while context is fresh
  2. Include alternatives: Show what was considered and why it wasn't chosen
  3. Track superseded decisions: Update status when decisions change
  4. Link related decisions: Use relations to show dependencies
  5. Review periodically: Check if old decisions are still valid