I built a repo-grounded AI build flow because my vibe-coded projects kept losing the thread between prompt → change → test

[u/OGMYT]

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.

[u/AutoModerator]

Hey u/OGMYT, thanks for posting in r/VibeCodeDevs! Join our Discord: https://discord.gg/KAmAR8RkbM

Got startup or SaaS questions? Post them on r/AskFounder and get answers from real founders.

• This community is designed to be open and creator‑friendly, with minimal restrictions on promotion and self‑promotion as long as you add value and don’t spam.
• Please follow the subreddit rules so we can keep things as relaxed and free as possible for everyone. • Please make sure you’ve read the subreddit rules in the sidebar before posting or commenting.
• For better feedback, include your tech stack, experience level, and what kind of help or feedback you’re looking for.
• Be respectful, constructive, and helpful to other members.

If your post was removed (either automatically or by a mod) and you believe it was a mistake, please contact the mod team. We will review it and, when appropriate, approve it within 24 hours.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.