rc-workflow-memorylisted

# Workflow Memory Maintain the workflow memory files provided by the caller. ## Required Inputs - Workflow memory directory path. - Shared workflow memory file path. - Current task memory file path. - Optional caller signal indicating whether either file must be compacted before proceeding. ## Workflow 1. Load the memory state before editing code. - Read the shared workflow memory file and the current task memory file before making any code change. - Treat these files as mandatory context for the run, not optional notes. - If the caller marks either file for compaction, compact that file per the Compaction Rules before proceeding with implementation. 2. Keep memory current while the task runs. - Update the current task memory whenever the objective changes, a non-obvious decision is made, an important learning appears, or an error changes the plan. - If the `rc-memory` skill has promoted high-confidence instincts (recurring trigger→action patterns for this project), treat them as a source of durable cross-task context worth carrying in shared memory. 3. Close out the run cleanly. - Update memory before any completion claim, handoff, or commit. - Record only facts that help the next run start faster and with fewer mistakes. ## Critical Rules - Do not invent history, decisions, or status that did not happen. - Do not copy large code blocks, stack traces, or task specs into memory files. - Do not duplicate facts that are obvious from the repository,