audit
Audit `.flow/memory/` entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry
Manually trigger plan-sync to update downstream task specs after implementation drift
> /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.
/syncContext preview
What this command does when you run it.
Manually trigger plan-sync to update downstream task specs after implementation drift
name: sync description: Manually trigger plan-sync to update downstream task specs after implementation drift argument-hint: "<id> [--dry-run]"
The ONLY purpose of this command is to call the `flow-next-sync` skill. You MUST use that skill now.
**Arguments:** $ARGUMENTS
Pass the arguments to the skill. The skill handles the sync logic.
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