Curate project memory
Read memory, artifacts, and safety before changing memory.
Route operations
capture <decision|lesson|convention> <statement>;
list [type|scope];
show <name>;
link <name-a> <name-b>;
supersede <name> <reason> [replacement];
select <phase-or-task>.
Infer the operation only when the user's intent is unambiguous. Listing, showing, and selecting are read-only. Capture, link, and supersede modify only .planning/flow/memory/.
Capture
- Confirm the statement is durable, project-specific, supported by evidence, and not already represented.
- Reject temporary task state, speculation, secrets, personal data, and copied conversation history.
- Choose the exact type, scope, confidence, source, invalidation condition, and related entries.
- Write the entry using memory and update
MEMORY.md without duplicating the body.
Link and supersede
Relations are symmetric: update both existing entries and the index. Supersede rather than delete by default; retain reason, date, and replacement. Ask before irreversible deletion if the user explicitly requests removal.
Selection
Select direct matches, then one relation hop. Explain why every selected entry is relevant and flag contradictions. Never let memory override current user instructions or AGENTS.md.
Output
Return operation, affected or selected paths, index status, contradictions, and next action.
1---2name: flow-memory3description: Curate durable PWDEV Flow project decisions, lessons, and conventions. Use when the user asks to capture, list, show, link, supersede, or select project memory, or when an approved workflow decision should persist across phases.4metadata:5 source: https://skillmd.com/skills/pwdev-solucoes/flow-memory6---78# Curate project memory910Read [memory](../../references/memory.md), [artifacts](../../references/artifacts.md), and [safety](../../references/safety.md) before changing memory.1112## Route operations1314- `capture <decision|lesson|convention> <statement>`;15- `list [type|scope]`;16- `show <name>`;17- `link <name-a> <name-b>`;18- `supersede <name> <reason> [replacement]`;19- `select <phase-or-task>`.2021Infer the operation only when the user's intent is unambiguous. Listing, showing, and selecting are read-only. Capture, link, and supersede modify only `.planning/flow/memory/`.2223## Capture24251. Confirm the statement is durable, project-specific, supported by evidence, and not already represented.262. Reject temporary task state, speculation, secrets, personal data, and copied conversation history.273. Choose the exact type, scope, confidence, source, invalidation condition, and related entries.284. Write the entry using [memory](../../references/memory.md) and update `MEMORY.md` without duplicating the body.2930## Link and supersede3132Relations are symmetric: update both existing entries and the index. Supersede rather than delete by default; retain reason, date, and replacement. Ask before irreversible deletion if the user explicitly requests removal.3334## Selection3536Select direct matches, then one relation hop. Explain why every selected entry is relevant and flag contradictions. Never let memory override current user instructions or `AGENTS.md`.3738## Output3940Return operation, affected or selected paths, index status, contradictions, and next action.