Memory Migrate
/flow-next:memory-migrate converts pre-fn-30 flat memory files into the categorized schema that current flow-next expects.
Old flow-next stored memory as three flat markdown files at .flow/memory/: pitfalls.md, conventions.md, decisions.md. fn-30 introduced one-entry-per-file with track / category / module / tags / status frontmatter, but the flat files persisted and became invisible to memory list, memory search, and /flow-next:audit.
When to use it
Section titled “When to use it”- The repo has
.flow/memory/pitfalls.md,conventions.md, ordecisions.mdat the root. /flow-next:auditreported a non-zero “legacy entries skipped” count.- Search and scout skills do not surface entries you remember writing.
If no legacy files exist, nothing happens — the skill exits cleanly.
How it classifies
Section titled “How it classifies”Each entry gets a mechanical default (track, category) from the source filename:
| Source | Default track | Default category |
|---|---|---|
pitfalls.md | bug | build-errors |
conventions.md | knowledge | patterns |
decisions.md | knowledge | decisions |
The host agent overrides the default only when the entry body unambiguously points elsewhere. An entry titled “race condition in worker pool” inside pitfalls.md clearly warrants bug/runtime-errors, not the mechanical bug/build-errors.
| Mode | Behavior |
|---|---|
| Interactive (default) | Ask via blocking question when an entry’s content suggests overriding the mechanical default. Confirm cleanup before renaming originals. |
Autofix (mode:autofix) | No user questions. Accept mechanical defaults except where the body unambiguously overrides them. Mark genuinely ambiguous entries as needs-review in the report. |
A scope hint after the mode token (e.g. pitfalls.md) narrows the migration to one legacy file.
After migration
Section titled “After migration”Originals stay in place by default until you confirm cleanup. The interactive mode offers a rename to *.md.legacy so the files remain readable but are clearly not the current source of truth. Autofix mode default-declines this and surfaces the suggestion as a recommendation.
/flow-next:audit will now find every entry. Run it after migration if the legacy files were old enough that some entries are likely stale.
What this is not
Section titled “What this is not”- Not a content rewrite. The migration preserves the original wording verbatim, only adding schema. Quality review is the audit’s job.
- Not destructive. Nothing is deleted automatically; cleanup is always a separate confirmation.
Next step
Section titled “Next step”/flow-next:audit