cy-workflow-memory

Maintains workflow-scoped task memory files for Compozy PRD task executions.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/j0ruge/LouvorFlow --skill cy-workflow-memory-j0ruge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-workflow-memory
Source: https://github.com/j0ruge/LouvorFlow/tree/main/skills/cy-workflow-memory
Command: npx skills add https://github.com/j0ruge/LouvorFlow --skill cy-workflow-memory-j0ruge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long-running agent workflows lose context between task runs, causing repeated mistakes, rediscovery of known constraints, and inconsistent decisions. This Skill keeps workflow memory files current so each Compozy PRD task run starts with the right durable context. ## Core Features & Use Cases - Memory Loading and Updating: Reads shared workflow memory and current task memory before code changes, then updates them as objectives, decisions, and learnings evolve. - Promotion Discipline: Applies a three-question test to decide which facts move from task memory into shared cross-task memory. - Compaction: Rewrites noisy or repetitive memory files into short factual bullets while preserving decisions, risks, and handoffs, guided by references/memory-guidelines.md. - Use Case: During a multi-task PRD implementation, an agent records a discovered API rate limit in shared memory so every subsequent task respects it without rediscovering the constraint. ## Quick Start Read the shared workflow memory and current task memory files at the provided paths, keep them updated during this task, and compact them if flagged before finishing.

Frequently Asked Questions about cy-workflow-memory

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

FAQPage Schema
How do I maintain agent memory across multiple workflow task runs?▼

Read the shared workflow memory and current task memory before editing code, update task memory as decisions and learnings occur, and promote only durable cross-task facts to shared memory. Update both files before any completion claim or handoff.

What belongs in shared workflow memory versus task memory?▼

Shared memory holds durable cross-task context like constraints, architectural decisions, and open risks. Task memory holds operational details like the current objective, touched files, and task-specific debugging steps.

When should workflow memory files be compacted?▼

Compact when the caller flags a file or when it has grown noisy and repetitive. Preserve current state, decisions, learnings, risks, and handoffs while removing repetition, stale notes, and facts derivable from the repository or PRD.

What happens if a provided memory file path is missing?▼

The agent stops and reports the mismatch instead of guessing another path. It never invents memory content or substitutes a different file location.

When should this skill not be used?▼

Do not use it for PR review remediation, global user preferences, or programmatic event-log summarization. It is scoped strictly to workflow memory maintenance during Compozy PRD task executions.