memory

Name: memory
Availability: InStock
Author: khairulariffinka

Load module context and sync decisions into local and global diaries.

1|Updated Apr 12, 2026

Search Tags:#planning #context #memory #persistence #state-management #modular #diary

Ready to run

npx skills add https://github.com/khairulariffinka/codexen --skill memory-khairulariffinka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/khairulariffinka/codexen/tree/main/core/skills/memory
Command: npx skills add https://github.com/khairulariffinka/codexen --skill memory-khairulariffinka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent project memory and global diary management to keep context, decisions, and module states in sync across your workspace.

Core Features & Use Cases

Load and isolate module context from AGENTS.md, current-state.md, and per-module context files.
Sync planner progress and mirror decisions into a unified work diary for both local and global scopes.
Save session data automatically to support cross-project memory and long-term archival.

Quick Start

Ask memory to load the current context for a module and preview its state.

Frequently Asked Questions about memory

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

FAQPage Schema

How do I maintain persistent project memory across multiple modules?▼

Persistent project memory is maintained by reading context from AGENTS.md and current-state.md, updating planner.md, and saving session data locally and globally to keep module states in sync.

How does modular context loading work for project diaries?▼

Modular context loading works by reading and isolating context from AGENTS.md, current-state.md, and per-module context files, then mirroring decisions into a unified work diary for local and global scopes.

What is the best way to sync planner progress with a unified work diary?▼

Syncing planner progress involves coordinating modular context loading and decision mirroring into a unified work diary, ensuring local and global diary updates stay aligned across your workspace.

Can I save session data automatically for cross-project memory and archival?▼

Yes, session data is saved automatically to support cross-project memory and long-term archival, coordinating updates across local and global diary scopes.

Do I need AGENTS.md and current-state.md files to manage project state?▼

Yes, AGENTS.md and current-state.md are required as input sources for loading and isolating module context before updating planner progress and syncing diary states.

When do I need unified diary management for my project workspace?▼

Unified diary management is needed when you must keep context, decisions, and module states in sync across multiple modules within a persistent project memory workspace.