# Manage Project Memory and Plans

AI-assisted projects can lose decisions, patterns, and task state across sessions. This skill maintains SSOT memory files and migrates workflow documents with backups.

## Install

```bash
npx skillstore add chachamaru127/memory
```

## Metadata

- - Slug: chachamaru127-memory
- - Version: 1.0.0
- - Author: Chachamaru127
- - GitHub username: Chachamaru127
- - License: MIT
- - Repository: https://github.com/Chachamaru127/claude-code-harness/tree/main/skills/memory
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: external\_commands, filesystem
- - Quality score: 77
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/chachamaru127-memory
- - Manifest: https://skillstore.pages.dev/api/skills/chachamaru127-memory/manifest

## Capabilities

- Routes memory, SSOT, Plans.md merge, and workflow migration requests to focused subskills.
- Initializes decisions.md, patterns.md, and optional session-log.md under .claude/memory.
- Merges Plans.md while preserving WIP, TODO, done, and archive task sections.
- Migrates AGENTS.md, CLAUDE.md, and Plans.md after user confirmation.
- Creates backups before workflow file migration and summarizes resulting diffs.

## Use Cases

- Initialize Team Memory: Create shared decision and pattern files before a new project gains complex history.
- Preserve Task State: Update Plans.md structure without losing active, pending, completed, or archived tasks.
- Migrate Workflow Docs: Move AGENTS.md, CLAUDE.md, and Plans.md into a newer format while keeping important rules.

## Prompt Templates

### Initialize Memory

```
Initialize the project memory SSOT files. Create missing decisions.md, patterns.md, and session-log.md files without overwriting existing files.
```

### Merge Plans Safely

```
Merge the current Plans.md into the latest structure. Preserve all existing task sections and report the task counts.
```

### Review Migration Inputs

```
Review AGENTS.md, CLAUDE.md, and Plans.md for migration. Summarize rules and tasks first, then ask what must be preserved.
```

### Migrate With Verification

```
Migrate the workflow files after confirmation. Create backups, preserve project-specific rules, show the diff summary, and wait for final review.
```

## Limitations

- It manages project documentation, not application source code.
- It depends on existing templates and recognizable Plans.md section markers.
- It may edit files that influence future assistant behavior.
- It does not provide a database-backed or cloud-synced memory system.

## Best Practices

- Review existing memory and workflow files before approving migration.
- Keep shared decisions and patterns under version control when appropriate.
- Inspect the diff summary before accepting rewritten workflow documents.

## Anti Patterns

- Use this skill for ordinary implementation or code review work.
- Approve migration without checking which project rules will be preserved.
- Treat session logs as shared SSOT when they contain local notes.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T20:10:27.527\+00:00
- - Summary: Static command-execution and weak-crypto findings are false positives caused by Markdown examples, inline paths, YAML frontmatter, and Japanese text entropy. No prompt injection, network access, credential access, or obfuscated payload behavior was found. The skill is publishable with low risk because it intentionally edits local workflow files and may use local Bash commands for backups and diffs.

## Stats

- - Views: 202
- - Downloads: 5
- - Favorites: 0
- - Popularity score: 0