Usage:
> flow feature create 'implement csv exports' --model opus --effort high
• triage → plan → git worktree → code → verify → CI → review → merge
• pauses only for plan approval and subjective pre-merge validation (if any)
> flow epic create 'design app for making money' --model haiku --effort low
• (same flow as `feature` but it only produces an epic PRD with phase dependency mappings)
> flow epic run design-app-for-making-money
• resolves current state of the epic and launches feature pipelines for unblocked phases
> claude -p "Triage this list of bugs and launch a flow pipeline for each bundle with opus high: <bug list>"
• a flow pipeline can create new flow pipelines so fan-out is really powerful (eg if one pipeline discovers a bug that should be handled separately)
> flow feature ls # show all active pipelines
> flow epic ls # show all epic statuses
Stats:
• in the last 4 months I've merged ~1000 heavily tested/reviewed PRs
I very strongly recommend enabling the tmux integration and learning how to use tmux if you don't already.