session-memory
Session Memory Skill
Purpose
Restore full working context from persistent memory automatically at session start. This prevents loss of context from previous sessions, crashes, or context window resets.
When to Activate
MANDATORY at session start - This skill should activate automatically when:
- User starts a new coding session
- Context has been reset or compacted
- User returns to a project after time away
- User asks "what was I working on?" or similar
DO NOT ask permission - Just use it. The user expects context restoration.
Orchestration Steps
1. Immediate Context Recall (First Action)
Call: recall({ days: 7, limit: 20 })
More from anortham/goldfish
recall
Restore context from Goldfish developer memory — use when starting a new session, after context loss, searching for past work, or when the user asks what happened previously, wants to find old decisions, or needs cross-project context
13plan
Create and manage persistent plans in Goldfish memory — use when starting multi-session work, making architectural decisions, or when the user discusses project direction, roadmaps, or design decisions that need to persist across sessions
13plan-status
Assess progress against the active Goldfish plan using checkpoints and plan data — use when the user asks about project progress, how things are going, what's been accomplished, or wants a status check against their plan
12checkpoint
Save developer context to Goldfish memory — checkpoint at meaningful milestones, not after every action
12standup
Generate a standup report from Goldfish memory across all projects — use when the user asks for a standup, daily update, progress summary, what they've been working on, or needs a report for a team sync
11progress-tracking
Proactively checkpoint work progress at key moments without asking permission. Use when completing tasks, fixing bugs, making discoveries, or reaching milestones. Builds persistent memory across sessions.
2