memory-workflow

Define and enforce a structured data workflow with memory system separation.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/eysenfalk/git-review --skill memory-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-workflow
Source: https://github.com/eysenfalk/git-review/tree/main/.claude/skills/memory-workflow
Command: npx skills add https://github.com/eysenfalk/git-review --skill memory-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of managing different types of data and memory systems within a project, ensuring clarity, avoiding duplication, and optimizing how information is stored and retrieved across sessions.

Core Features & Use Cases

  • Data Workflow Enforcement: Establishes a clear, linear flow for requirements, status, and acceptance criteria, directing content to specific memory systems.
  • Memory System Separation: Defines distinct purposes for claude-mem, Claude-Flow, Serena, and Linear to prevent overlap and ensure efficient data management.
  • Use Case: When making a significant architectural decision, this Skill ensures it's logged in claude-mem for cross-session context, while the detailed requirements remain in Linear, preventing redundant data entry.

Quick Start

Use the memory-workflow skill to save a new architectural decision to claude-mem.

Frequently Asked Questions about memory-workflow

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

FAQPage Schema
How do I maintain agent context and decision logging across multiple sessions?

To separate memory systems for agentic operations, define distinct purposes for each tool to prevent overlap. Direct requirements to project management tools and architectural decisions to cross-session memory stores to avoid redundant data entry.

What is the best way to structure data workflow for multi-agent coordination?

A 3-layer workflow structure manages memory observations efficiently by separating cross-session decision memory, agent coordination patterns, and project management tracking into distinct access layers.

How does memory system separation improve project management tracking?

Memory system separation prevents data duplication by routing architectural decisions to cross-session memory while detailed requirements remain in project management tools. This ensures efficient data retrieval and clear workflow enforcement.

How do I enforce a linear data workflow for requirements and status updates?

Enforcing a linear data workflow requires directing requirements and status content to designated memory systems. This separation ensures efficient data management and retrieval during agentic operations.

Can I use a 3-layer workflow to manage memory observations efficiently?

A 3-layer workflow optimizes memory observation access by separating cross-session decisions, agent coordination, and project tracking. This structure enforces a clear data workflow and prevents memory system overlap.

Why do I need to separate cross-session decision memory from project management tools?

You need to separate cross-session decision memory to avoid duplication and ensure clarity. Logging architectural decisions in dedicated memory stores while keeping requirements in project tools optimizes information retrieval.