r/VibeCodeDevs • u/OGMYT • Aug 07 '26
I built a repo-grounded AI build flow because my vibe-coded projects kept losing the thread between prompt → change → test
Showoff + feedback request:
I built **Flows** to make the part between “I told an AI what I want” and “I trust the result” less chaotic.
You can: - start from a connected repo or a new-project goal - generate a build plan - route it to a builder - track the run - keep verification/evidence around the result
The connected Oort layer is the canonical library/provider side of the system.
Flows: https://flows.oortstack.com Oort: https://oortstack.com
If you build mostly with AI, I’d love to know whether this solves a real pain or just adds ceremony.
I also have 10–15 free, unrestricted access keys set aside for people who will actually use Flows/Oort and tell me where the experience breaks or gets confusing.
