memory-management

Audit project memory and resolve conflicts via memory_read, memory_append, and memory_replace.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/jralph/.config-opencode --skill memory-management-jralph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-management
Source: https://github.com/jralph/.config-opencode/tree/main/skills/memory-management
Command: npx skills add https://github.com/jralph/.config-opencode --skill memory-management-jralph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams maintain a clean, conflict-free living memory of project decisions, patterns, and constraints to ensure consistent guidance and faster onboarding.

Core Features & Use Cases

  • Memory Audit & Hygiene: Implements regular checks, identifies duplicates, conflicts, and obsolete patterns, and archives outdated content.
  • Conflict Resolution & Governance: Provides structured workflows to resolve contradictions between rules and align with current codebase.
  • Archival & Record-Keeping: Moves outdated memory entries to an archive with rationale and dates for future audits.
  • Operational Memory Writing: Guides engineers to write focused, actionable memory entries when decisions are made.

Quick Start

Start a memory audit by reading the current project memory, resolve any conflicts, and record approved decisions using the memory_read, memory_append, and memory_replace commands.

Frequently Asked Questions about memory-management

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

FAQPage Schema
How do I resolve conflicts in project memory and keep knowledge base entries aligned with the codebase?

Conflict resolution in project memory is handled through structured governance workflows that identify contradictions between rules and update outdated guidance to align with the current codebase. This ensures knowledge base entries remain consistent.

What is the best way to audit project memory for duplicate or obsolete architectural decisions?

A memory audit identifies duplicates, conflicts, and obsolete patterns within project memory. Outdated architectural decisions are then moved to a memory archive with rationale and dates to maintain a clean knowledge base.

How do I write actionable project memory entries when architectural decisions are made?

Operational memory writing guides engineers to record focused, actionable memory entries using the memory_append command, ensuring that decisions are captured cleanly without creating conflicts or outdated guidance.

When should I archive outdated memory entries instead of deleting them?

Outdated memory entries should be archived rather than deleted to preserve rationale and dates for future audits. The memory_replace command updates the active knowledge base while the archival process retains the historical record.

Can I use memory management commands without dependencies for team onboarding?

Yes, memory management requires no external dependencies. It uses memory_read, memory_append, and memory_replace commands to maintain a living memory of project decisions, ensuring faster onboarding and consistent guidance.