Field Notes
Flow-Next is field-hardened: it runs inside enterprise coaching engagements worldwide - from CAD and construction software to proptech and education - and in the open.
From the field
Section titled “From the field”Discovery compresses hard. A 2-3 hour structured discovery interview reliably produces 8-11 implementation-ready specs - numbered acceptance criteria, boundaries, task breakdowns. The backlog conversation that used to take a sprint of refinement ceremonies becomes an afternoon with an interview transcript and /flow-next:interview.
Product and engineering leads see the delta first. Across engagements, their verdicts converge on the same two observations: a clear efficiency gain, and edge cases surfaced during spec review that the team would otherwise have met in production. The spec-review stage moves the argument to the cheapest possible moment - before any code exists.
It runs where enterprises actually live. GitHub Enterprise and GitLab. Jira-driven planning on the tracker bridge. Modern monorepos and hundred-repo microservice estates next to decades-old legacy codebases - Windows included. The zero-dependency, repo-local design is not an aesthetic choice - it is what survives enterprise IT.
The honest asymmetry
Section titled “The honest asymmetry”Adoption is not uniformly euphoric, and pretending otherwise would cost this page its credibility. The consistent pattern: product and delivery roles feel relief early - specs they can read, evidence they can audit, progress they can see. Senior developers feel friction early - the pipeline formalizes judgment they already exercise implicitly, and the ceremony reads as overhead until the first review gate catches something they would have missed. The friction fades with the first caught regression; the relief does not.
In the open
Section titled “In the open”The open-source record is linkable, so it speaks in its own words:
“I am enjoying your version of all these cool new plugins. So far yours has worked the best.”
“Hello, really enjoying this project, thanks for making it and making it public (also huge compliments on your website!)”
“it’s been really useful in my workflow.”
Beyond quotes:
- External kernel contributions - PR #95 is an outside contributor shipping a correct
flowctlfix: adoption deep enough to patch the CLI. - Featured in awesome-claude-code-workflows - cited for plan-first workflows, Ralph autonomous mode, and receipt-based gating (#96).
- CI on all three OSes - the test matrix runs Linux, macOS, and Windows on every push, because the field runs all three.
Reading the evidence yourself
Section titled “Reading the evidence yourself”Everything the pipeline produces is inspectable in any repo that runs it: specs with numbered criteria under .flow/specs/, review receipts under .flow/review-receipts/, evidence JSON on every completed task. The verification spine explains the system; a week of running it produces your own field notes.