memory-curator

Consolidate project state from AGENTS.md and logs into memory/MEMORY.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wendeus0/AI-dotfiles --skill memory-curator-wendeus0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-curator
Source: https://github.com/wendeus0/AI-dotfiles/tree/main/core/skills/memory-curator
Command: npx skills add https://github.com/wendeus0/AI-dotfiles --skill memory-curator-wendeus0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidate the durable memory of a project into memory/MEMORY.md, capturing the current progress, fronts, decisions, and open items to keep a stable, reusable record that survives sessions.

Core Features & Use Cases

  • Reads AGENTS.md, memory/MEMORY.md, PENDING_LOG.md and ERROR_LOG.md to extract the working memory and session context.
  • Updates memory/MEMORY.md with a lean index of project state, active fronts, stable decisions, and next steps without turning into a transcript.
  • Generates a concise handoff document when a session ends so the next user can resume quickly.
  • Enforces safe boundaries by not making backlog decisions or altering operational logs beyond the designated memory store.

Quick Start

Execute memory-curator to consolidate the durable project memory into memory/MEMORY.md and prepare a handoff.

Frequently Asked Questions about memory-curator

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

FAQPage Schema
How do I maintain durable project memory across coding sessions?

To maintain durable project memory across sessions, consolidate working context from AGENTS.md, PENDING_LOG.md, and ERROR_LOG.md into a lean memory/MEMORY.md file that survives across different runtime instances.

What is the best way to generate a session handoff document for project state?

Generating a session handoff document involves reading existing project logs and memory files to extract a snapshot of current progress, stable decisions, and open items, producing a concise record for the next user to resume quickly.

How does memory consolidation handle pending tasks and error logs?

Memory consolidation extracts context from PENDING_LOG.md and ERROR_LOG.md while enforcing safe boundaries, keeping operational details in their dedicated logs and updating only the designated memory store without making backlog decisions.

Can I use project memory files to track active fronts without creating a transcript?

Yes, the system updates memory/MEMORY.md with a lean index of project state, active fronts, and stable decisions, specifically enforcing rules to prevent the memory file from turning into a detailed session transcript.

When should I explicitly invoke session closure for project handoffs?

You should explicitly invoke session closure when you need to end a runtime instance and generate a handoff, as the system requires explicit invocation to consolidate the current project state and close the ongoing session safely.

What are the limitations of automated project state consolidation?

Automated project state consolidation is limited by strict boundaries: it does not make backlog decisions, does not alter operational logs beyond the designated memory store, and requires explicit invocation to close or end a session.