save-session

Saves session context and decisions to project memory files for future sessions.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/SSS08099/mom-system --skill save-session-sss08099
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-session
Source: https://github.com/SSS08099/mom-system/tree/main/.agents/skills/save-session
Command: npx skills add https://github.com/SSS08099/mom-system --skill save-session-sss08099

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When switching between chat sessions, important context like architecture decisions, new patterns, and progress is lost. This Skill preserves that context by writing it to structured memory files so the next session can resume where the previous one stopped. ## Core Features & Use Cases - Session Summarization: Scans the conversation for new features, architecture decisions, patterns, bug fixes, and data model changes, then appends a dated summary to project-progress.md. - Memory File Creation: Creates new memory files with YAML frontmatter (name, description, type) for reusable patterns, major design decisions, and significant module changes. - Index Maintenance: Updates the MEMORY.md index and links related memories with [[name]] references, while filtering out trivial changes like typos and one-time fixes. - Use Case: Before closing a long coding session where you built a new export feature and refactored the search layout, ask the assistant to save the session so tomorrow's session starts with full context. ## Quick Start Save this session's progress and decisions to memory before I switch to a new chat window.

Frequently Asked Questions about save-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save chat session context for future AI sessions?

Ask the assistant to save the session before switching chat windows. It scans the conversation for features, decisions, and patterns, then writes them to project-progress.md and structured memory files that the next session can read.

What gets saved when preserving a coding session to memory?

New features, architecture decisions, reusable patterns, data model changes, and configuration changes are saved. One-time bug fixes, typos, trivial UI tweaks, and items already documented elsewhere are explicitly excluded.

What format do session memory files use?

Memory files are Markdown with YAML frontmatter containing a name, one-line description, and a type field (project, feedback, reference, or user). The body includes the content plus Why and How to apply sections.

Does saving a session overwrite previous memory files?

No. The Skill reads existing memory files first and appends dated sections rather than overwriting. New memories are linked to related ones using [[name]] references, and MEMORY.md is updated only when new files are created.

When should I not save session context to memory?

Skip saving when the session only involved one-time bug fixes, trivial UI tweaks, normal development iteration, or work already recorded in AGENTS.md or known-issues documentation.