memory-conventions

name	memory-conventions
description	Guide for storing and retrieving institutional knowledge using Copilot built-in memory. Use when an agent needs to persist decisions, research, audit trails, or preferences to the correct memory scope with proper attribution.
argument-hint	What to store or retrieve (e.g., "store research finding", "retrieve past decisions on tech sector")

Memory Conventions

When to Use

• Storing research findings, decisions, or audit entries after a workflow completes
• Retrieving past research or decisions for context in new analysis
• Setting up memory path conventions for a new agentic system
• Checking what institutional knowledge exists on a topic

Procedure

1. Determine the memory operation: store or retrieve
2. Select the correct scope using the memory schema reference:
   • /memories/repo/ — Institutional knowledge: decisions, research, playbooks, audit trail. Persists across conversations.
   • /memories/session/ — Active context: current research, in-progress analysis. Cleared after conversation.
   • /memories/ — User preferences: methodology, risk tolerance, notification prefs. Persists across workspaces.
3. For store operations:
   • Format the entry following the attribution schema
   • Use the path convention: /memories/repo/{category}/{topic}-{date}.md
   • Write via #tool:memory with create command
   • Verify the entry was stored correctly
4. For retrieve operations:
   • View the target directory via #tool:memory with view command
   • Read specific entries for relevant context
   • Summarize findings for the requesting agent
5. For search operations:
   • List directory contents to find relevant entries by topic or date
   • Read matching entries and extract relevant sections

Validation Checklist

• Correct memory scope selected (repo/session/user)
• Path follows naming convention: {category}/{topic}-{date}.md
• Attribution metadata included (Date, Agent, Sources, Tags, Context)
• No duplicate entries — check existing files before creating
• Sensitive data not stored in user memory (use repo memory instead)