flow-note

You can capture design corrections without interrupting your workflow by appending notes directly into a local state file. This preserves learnings across team discussions and prevents knowledge loss during collaborative development sessions.

A FLOW state file is a local JSON file used to preserve learnings and corrections across development sessions. You need it when working in multi-engineer collaboration environments where knowledge must be stored for future reference without disruption.

You store lessons by invoking a note-capture command that appends your takeaway to the branch state file. This allows subsequent work on that branch to recall the stored learnings and apply them immediately.

Yes, this state management approach is specifically designed for collaborative development sessions across multiple engineers and worktrees. It ensures that learnings are preserved in the local state file for the entire team.

The best way to prevent knowledge loss is to capture corrections and clarifications into a persistent local state file. This creates a searchable reference for future sessions, stopping repeated misunderstandings among the team.

Yes, you need access to a local state file located at a specific branch path within a flow-states directory. This file structure is required to append notes without disrupting your current development session.