Throughout my career I've worked on many different teams that often spanned many different projects and repos. Sometimes the tech stack was similar but naturally the tooling and development process grew in different directions. Whenever I onboarded onto a new project I'd spend a bunch of time just trying to figure out how to build, deploy, and maintain it. It was great when projects had an up-to-date Makefile or README, but that wasn't always the case. Sometimes developer runbooks were floating around in Slack or some wiki, far from the code. I started running into this same problem on my own side projects and home lab outside of work too.

About 3 years ago I started building Flow to solve this. I landed on a Go CLI that lets you define tasks in YAML and register your projects as workspaces, giving you easily searchable, auto-generated documentation through a TUI. Over time it grew into more than I planned; a local secret vault, a templating engine, and an MCP server so tools like Claude Code can browse and run your workflows natively.

Over the last year AI has been generating even more scripts, packages, and scaffolded repos for me making the problem noticeably worse. That pushed me to start thinking about Flow differently. Not just as a tool for me or teammates onboarding onto a project, but as a documentation and orchestration layer that agentic coding tools can actually use. I just shipped the biggest release yet and would love feedback from other engineers, especially anyone who's hit this same wall.

Check out all that Flow has to offer: - Documentation: https://flowexec.io - GitHub: https://github.com/flowexec/flow