audit
Audit `.flow/memory/` entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry
Migrate legacy `.flow/memory/{pitfalls,conventions,decisions}.md` flat files into the categorized YAML schema — host agent classifies each entry directly
> /plugin marketplace add gmickel/flow-next > /plugin install flow-next@flow-next
How it fires
How this command gets triggered: by you, by Claude, or both.
/memory-migrateContext preview
What this command does when you run it.
Migrate legacy `.flow/memory/{pitfalls,conventions,decisions}.md` flat files into the categorized YAML schema — host agent classifies each entry directly
name: memory-migrate
description: Migrate legacy `.flow/memory/{pitfalls,conventions,decisions}.md` flat files into the categorized YAML schema — host agent classifies each entry directly
argument-hint: "[mode:autofix] [optional scope hint — e.g. pitfalls.md]"The ONLY purpose of this command is to call the `flow-next-memory-migrate` skill. You MUST use that skill now.
**Arguments:** $ARGUMENTS
Pass the arguments to the skill verbatim. The skill handles mode detection (`mode:autofix` token), legacy-file detection, per-entry classification, categorized writes, verification, and optional cleanup.
Repeatable agentic engineering. The workflow layer that turns AI coding agents into a disciplined factory: durable specs, fresh-context workers, adversarial cross-model reviews, receipts. Everything in your repo, zero dependencies. Claude Code · Codex · Cursor · Droid.
Audit `.flow/memory/` entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry
Synthesize the current conversation into a flow-next spec at `.flow/specs/<spec-id>.md` — source-tagged, saved-spec review, no silent overwrite
Decision-map discovery for one oversized/unclear idea before capture - ground, chart a frontier, resolve one decision per invocation, brief for capture
Seed or maintain the committed user-POV feature map at `.flow/features/`
Conductor - an idea or change request, a spec or task id, a tracker issue, a branch or path, a bug report, a how or why question, something slow, a…
John Carmack-level implementation review via RepoPrompt or Codex