Flow Patch

Triggered by: /flow-patch

For single bounded changes — too small for a full spec doc. Implement inline in this session so the user sees work in real time. Review after each task via subagents.

When to use

Use `/flow-patch`	Redirect to `/flow-spec`
≤3 files, one concern	>3 files or multiple concerns
Clear success criteria	Needs design exploration
Bug fix with known cause	Architectural change

Branch rule

Read and follow flow-shared/references/session-gate.md then flow-shared/references/branch-gate.md (resolve via path resolver in flow/SKILL.md). Session gate before any STATE write; branch and workspace confirmation before implementation.

Patch on main/master: use branch-gate On main menu (branch here vs worktree) — never commit patch work on main without explicit approval.