Slack Memory Retrieval

Memory Structure

The memory system uses a hybrid approach:

Profile Files (One Per Entity)

• channels/C123_마케팅팀.md - Channel guidelines, preferences, static info
• users/U456_김철수.md - User profile, communication style

Topic Files (Multiple Per Category)

• projects/신제품런칭.md - Project discussions
• decisions/AWS전환_20251117.md - Important decisions
• meetings/2025-11-17-Q4회의.md - Meeting notes
• misc/마케팅팀_일상_20251117.md - Casual conversations

Directory Structure

{memories_path}/
├── index.md              # START HERE - navigation and stats
├── channels/             # Channel profile files (one per channel)
├── users/                # User profile files (one per user)
├── projects/             # Project topic files (multiple)
├── tasks/                # Task records
├── decisions/            # Decision records (date-stamped)
├── meetings/             # Meeting notes (date-stamped)
├── feedback/             # User feedback
├── announcements/        # Important announcements
├── resources/            # Internal docs and guides
├── external/news/        # External information
└── misc/                 # Uncategorized conversations

Essential Rules

Always Start with Index

CRITICAL: Every retrieval session must begin by reading index.md:

view {memories_path}/index.md

The index provides:

• Navigation structure
• Statistics (total channels, users, active projects)
• Recent updates (10 most recent changes)
• Quick links to key information

This one-time read gives you the complete map of available memories.

Context-Driven Retrieval

Extract context from the conversation:

Channel Context:

Message in #마케팅팀 
→ Load: {memories_path}/channels/C123_마케팅팀.md
→ Check related_to metadata for connected info

User Context:

DM from @chulsoo
→ Load: {memories_path}/users/U123_김철수.md
→ Get communication_style, preferences

Project Context:

Question about "신제품 런칭"
→ Load: {memories_path}/projects/신제품런칭.md
→ Check milestones, status, participants

Keyword Context:

Question mentions "결정", "승인"
→ Search: {memories_path}/decisions/
→ Find relevant decision files

Efficient Loading Strategy

Tier 1: Always Load (if relevant)

• index.md (overview)
• Current channel file (if in channel)
• Current user file (if DM or mentioned)

Tier 2: Load as Needed

• Project files (if project mentioned)
• Decision files (if asking about decisions)
• Meeting notes (if asking about meetings)

Tier 3: Load Selectively

• Tasks (only if specifically asked)
• Resources (only if referenced)
• External news (only if relevant)

Don't over-fetch. Use directory listings first:

view {memories_path}/projects/
# See available projects before loading specific files

Retrieval Patterns

Pattern 1: Channel Response

When responding in a channel:

# 1. Load channel context
view {memories_path}/channels/{channel_id}_{channel_name}.md

# 2. Check for channel guidelines
# Extract: tone, response_time, key_topics

# 3. Apply guidelines to response
# Adjust tone, format based on channel preferences

Pattern 2: User-Specific Response

When responding to a specific user:

# 1. Load user profile
view {memories_path}/users/{user_id}_{name}.md

# 2. Check communication_style
# Extract: tone, detail_level, preferences

# 3. Personalize response
# Match user's preferred style and detail level

Pattern 3: Project Status Query

When asked about project status:

# 1. Find project file
view {memories_path}/projects/
view {memories_path}/projects/{project_name}.md

# 2. Check metadata
# status, priority, milestones, participants

# 3. Get related info
# Check related_to for decisions, meetings

# 4. Provide comprehensive update
# Current status + recent activity + next steps

Pattern 4: Decision History

When asked about past decisions:

# 1. Search decisions
view {memories_path}/decisions/

# 2. Load relevant decision file
view {memories_path}/decisions/{decision_name}.md

# 3. Extract key info
# decision_makers, rationale, alternatives_considered

# 4. Explain context
# Why decision was made + alternatives + outcome

Pattern 5: Task History

When asked about completed work:

# 1. Check completed tasks
view {memories_path}/tasks/completed/

# 2. Filter by assignee/date
# Look for relevant assignee, date range

# 3. Summarize work
# List tasks + effort + outcomes

Advanced Techniques

Cross-Referencing

Follow the trail of related information:

# In project file:
---
related_to:
  - decisions/기술스택선택.md
  - meetings/2025-10-20-기획회의.md
---

Load related files to build complete context.

Metadata Filtering

Use metadata to filter without reading entire files:

# List directory first
view {memories_path}/projects/

# Check filenames and metadata
# Only load files matching criteria:
# - status: in_progress
# - priority: high
# - participants: includes current_user

Temporal Context

Consider time-sensitivity:

# Recent Updates in index.md
→ Shows 10 most recent changes
→ Focus on these for "latest" questions

# File metadata: created, updated
→ Check dates to prioritize fresh info

Tag-Based Discovery

Use tags for discovery: