flow-next-memory-migrate

Migrate legacy memory files into a categorized YAML schema via flowctl.

674|52|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/gmickel/flow-next --skill flow-next-memory-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-next-memory-migrate
Source: https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/codex/skills/flow-next-memory-migrate
Command: npx skills add https://github.com/gmickel/flow-next --skill flow-next-memory-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating legacy memory files into a structured YAML schema automates the transformation from ad-hoc, flat notes to a consistent, query-friendly memory catalog.

Core Features & Use Cases

  • Automates triage and classification of legacy memory files across pitfalls, conventions, and decisions.
  • Writes categorized entries via flowctl memory add, preserving metadata and enabling reliable retrieval.
  • Supports interactive ambiguity resolution or autofix workflows for scalable migrations.

Quick Start

Run the memory migrate task to convert all legacy memory files into the categorized YAML schema.

Frequently Asked Questions about flow-next-memory-migrate

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

FAQPage Schema
How do I migrate legacy memory files into a structured schema?

The migration process triages and classifies legacy memory files across pitfalls, conventions, and decisions, then writes them as structured entries via flowctl memory add to preserve metadata and enable reliable retrieval.

Can I automatically categorize flat memory notes into YAML?

Automatically categorizing flat memory notes into YAML is supported by applying an autofix mode that processes all three legacy files in .flow/memory without requiring interactive input for each entry.

Do I need flowctl to migrate memory files?

You need flowctl to migrate memory files because the process requires the Flow runtime tools to write categorized entries via the flowctl memory add command and repository access to read legacy files.

What is the best way to handle ambiguity when migrating legacy memory?

Handling ambiguity when migrating legacy memory is managed through interactive ambiguity resolution workflows, allowing you to manually verify and triage classifications for pitfalls, conventions, and decisions.

Does migrating memory with autofix mode preserve original metadata?

Migrating memory with autofix mode preserves original metadata by writing categorized entries via flowctl memory add, which maintains the data integrity needed for reliable retrieval in the structured YAML schema.