writer-memory

Store structured narrative context in versioned, git-friendly JSON across AI sessions.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/officechbusinessservices-creator/CompliCore --skill writer-memory-officechbusinessservices-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writer-memory
Source: https://github.com/officechbusinessservices-creator/CompliCore/tree/main/packages/oh-my-claudecode/skills/writer-memory
Command: npx skills add https://github.com/officechbusinessservices-creator/CompliCore --skill writer-memory-officechbusinessservices-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Writer Memory Skill solves the challenge of losing continuity in long-form writing by persisting characters, relationships, scenes, world rules, and themes across AI sessions.

Core Features & Use Cases

It stores structured memory in a versioned, git-friendly JSON format (.writer-memory/memory.json) with auto-backups, supports Korean storytelling workflows, and provides tools for memory querying, synopsis generation, and scene planning across collaborators.

Quick Start

Initialize a new memory project with writer-memory init <project-name>, then begin populating characters, worlds, and scenes, and use the /writer-memory query command to retrieve context.

Frequently Asked Questions about writer-memory

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

FAQPage Schema
How do I persist character memories and world-building context across AI sessions for long-form writing?

Character memory tracking stores characters, relationships, scenes, world rules, and themes in a versioned JSON format with auto-backups. This supports cross-scene continuity for long-form writing and collaborative storytelling across multiple AI sessions.

What's the best way to maintain story continuity when collaborating on narrative projects across different sessions?

Maintaining story continuity across collaborators is done by storing structured narrative context in a git-friendly JSON format with auto-backups. This typed memory schema with versioning and validation supports tracking scenes and characters without losing consistency.

How do I initialize a memory project to track characters and scenes?

Initialize a memory project by running the init command to create a structured JSON file, then populate characters, worlds, and scenes. Use query commands to retrieve context, generate synopses, and plan scenes across writing sessions.

Does writer-memory support exporting narrative context for external synopsis generation and scene planning?

Yes, the memory schema includes export utilities supporting synopsis generation and scene planning. These tools query and retrieve stored narrative context for use across different writing projects and collaborative storytelling workflows.

Can I use a JSON-based memory manager for Korean storytelling workflows?

Yes, the memory manager modules support Korean storytelling workflows alongside standard narrative tracking. The system stores structured memory in a versioned JSON format, enabling cross-scene continuity regardless of the writing language used.

What are the limitations of relying on JSON files for persistent narrative context in collaborative storytelling?

JSON-based narrative context relies on CLI-like commands for querying and updates, requiring strict schema validation. While auto-backups and versioning mitigate data loss, large-scale collaborative storytelling may face synchronization challenges without proper git-friendly workflows.