memory-management

Organize project memory into HOT, WARM, and COLD tiers with automatic promotion and demotion.

Updated May 18, 2026

Search Tags:#audit #archival #wiki #privacy #memory-management #open-loops #hot-cache

Ready to run

npx skills add https://github.com/lucasloutayf/barberia-evolution --skill memory-management-lucasloutayf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory-management
Source: https://github.com/lucasloutayf/barberia-evolution/tree/main/.agents/skills/memory-management
Command: npx skills add https://github.com/lucasloutayf/barberia-evolution --skill memory-management-lucasloutayf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams maintain coherent project context across sessions by organizing data into HOT/WARM/COLD memory tiers, automatically promoting frequently used items, demoting stale data, and archiving historical materials with privacy safeguards.

Core Features & Use Cases

Three-tier memory lifecycle: HOT memory loads every session, WARM on demand, COLD archival.
Wiki index management: auto-refresh of memory/wiki/index.md and per-project compiled pages.
Auditable handoff and GDPR-compliant purges: supports auditor blocks and privacy tombstones per GDPR/CCPA rules.

Quick Start

Initialize the memory structure for a new project and seed the hot-cache with your top targets.

Frequently Asked Questions about memory-management

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

FAQPage Schema

How do I organize project memory into HOT, WARM, and COLD tiers?▼

Project memory is organized by automatically promoting frequently used items to a hot-cache, loading warm data on demand, and demoting stale data to cold archival with a wiki-backed audit trail.

How does wiki index management work for archived project data?▼

Wiki index management works by auto-refreshing the memory/wiki/index.md file and compiling per-project pages to ensure historical materials remain accessible and auditable across sessions.

Can I perform privacy-compliant data purges for GDPR and CCPA?▼

Yes, you can perform privacy-compliant purges by utilizing built-in auditor blocks and generating privacy tombstones to satisfy GDPR and CCPA deletion requirements.

What is the best way to maintain coherent project context across sessions?▼

Maintaining coherent context across sessions requires reading memory state and updating files like hot-cache.md, open-loops.md, and decisions.md, then emitting a handoff summary.

Does this memory management approach coordinate with other workflow skills?▼

Yes, memory management coordinates with other skills via designated triggers to handle archiving, purges, and tier promotion or demotion automatically across the workflow.

How do I track open loops and decisions in campaign memory?▼

You track open loops and decisions by updating memory/open-loops.md and memory/decisions.md directly during the memory state reading and handoff summary emission process.