memory-sync

Memory-sync systematically reviews code changes to identify impacts on architecture and conventions, then updates both AI memories (like project_overview.md) and human-readable documentation (like docs/PLAN.md) through a guided Phase 1–4 workflow, ensuring consistency across your project.

Synchronize after completing major development phases, implementing new architectural patterns, or discovering significant code changes. This prevents AI context and team documentation from diverging and keeps both sources of truth aligned.

AI memories are token-efficient summaries (project_overview.md, critical_implementation_patterns.md) for immediate AI context; project documentation is comprehensive, human-readable guidance (docs/ARCHITECTURE.md, docs/PLAN.md) for team understanding. Memory-sync maintains both strategically.

Memory-sync enforces token-efficient updates by applying targeted, file-specific memory and documentation adaptations rather than wholesale rewrites, balancing lean AI-optimized memories with detailed human-comprehensible docs.

Memory-sync is designed for projects with established documentation files like project_overview.md, codebase_structure.md, and docs/PLAN.md. It works best when your project already maintains separate AI memory and human documentation assets.

Memory-sync's consistency check identifies divergence by reviewing recent changes and flagging specific files that require updates, providing clear instructions for thorough revisions to realign both sources of truth.