memory-briefing

Project Briefing

Build a structured orientation from brain/ compiled knowledge, Remember session history, and vault notes.

Procedure

Step 1: Read brain/goals.md

Read brain/goals.md to establish current focus areas and active priorities. This is the ground truth for what matters right now — let it frame the entire briefing.

Step 2: Read brain/index.md for recent context

Read brain/index.md and locate the Recent Context section. This contains the last session summary compiled during wrap-up. Use it as the "last session" narrative in the briefing.

If brain/index.md is missing or the Recent Context section is empty, note this in the briefing: "brain/index.md not updated — last session summary unavailable."

Step 3: Check Remember timeline

Read the === REMEMBER === block from the current session context (injected by the Remember plugin at SessionStart). This contains identity, recent session buffer, and compressed summaries.

For additional granularity, read Remember's timeline files directly:

• .remember/now.md — immediate context
• .remember/today-*.md — today's captures (glob for the most recent)
• .remember/recent.md — compressed recent history

If the Remember block is thin or missing, note this: "Remember plugin inactive — session history unavailable."

Step 4: Read active project notes

Read relevant notes from 01-projects/ based on the topic named by the user. If the user said just "/briefing" with no qualifier, ask one question: "Which project — [list from brain/goals.md]?"

Look for:

• Project status and open questions
• Related decisions in 03-decisions/
• Related solutions in 02-solutions/

Read the most relevant 2-3 notes.

Step 5: Deepen context if needed (optional)

If Steps 1-4 leave significant gaps, use Nexus semantic search for depth:

Call mcp__nexus-personal__toolManager_useTools with:

• context.memory: "Searching vault for context"
• context.goal: "Find relevant vault notes for briefing"
• calls: [{ "agent": "searchManager", "tool": "searchContent", "params": { "query": "", "semantic": true } }]

Step 6: Synthesize briefing

Combine brain/ knowledge, Remember history, and vault notes into a structured briefing:

## Briefing: [Topic/Project]

### Current Focus
Active goals and priorities from brain/goals.md.

### Last Session
What happened. Key decisions. Where work stopped. (from brain/index.md Recent Context + Remember)

### Active Work
Relevant vault notes. Open questions. Known blockers.

### Next Steps
Prioritized actions based on goals and last session state.

### Gaps
Questions that need input before proceeding.

Step 7: Print summary

Show the briefing in chat. This is the primary output — keep it concise and scannable.

Step 8: Persist (optional)

Ask: "Save this briefing to the vault? [y/n]"

If yes, write to 05-journal/YYYY-MM-DD-briefing-<topic-slug>.md with frontmatter:

---
title: "Briefing: <Topic>"
date: YYYY-MM-DD
type: work-note
tags: [briefing, <project-tag>]
confidence: observed
related: ["[[<project-note>]]"]
source: "/claude-memory:briefing skill"
source-type: session
---

Commit: git add 05-journal/<filename> && git commit -m "vault: briefing — <topic>"