What problem does it solve?
It prevents duplicated or conflicting notes by defining where decisions, requirements, and observations must be stored across memory systems while enforcing an efficient workflow for saving and retrieving knowledge.
Core Features & Use Cases
- Data workflow enforcement: Keeps a single source of truth by routing requirements/specs/status/acceptance criteria to Linear comments while allowing local plan files only for implementation-level detail written by the planner agent.
- Memory system separation: Establishes clear ownership of information across claude-mem, Claude-Flow, Serena, and Linear to eliminate overlap and confusion.
- Efficient claude-mem retrieval workflow: Requires search-to-filter-to-get-observations sequencing to avoid unnecessary token usage, and defines when to save or avoid saving across sessions.
Quick Start
Use the memory-workflow skill when you need to record a cross-session architectural decision or capture an observation for future reuse without duplicating content that already belongs in Linear.
