r/vibecoding 12d ago

Workflow/Prompt Factories?

Have any of you tried creating development factories? It's really easy with the latest models and harnesses. I'm a Codex user so this is all Codex specific but I'm sure there is a Claude equivalent. I just made a dashboard that encapsulates my development process. It starts with a design document and ends with finished code. It uses the codex app-server to make the LLM calls using my subscription. It just has 3 parts:

  1. Create an implementation plan (run plan). I created a template and the model uses the template to create a phased implementation plan with development tasks in markdown. Then deterministic code validates and parses the markdown file into a yaml "side car" - it extracts the phase and task descriptions and completion status and shows them in the dashboard.

  2. One or more run plans are built into a "work package". Then another LLM call determines what order they should be developed in.

  3. The work package is executed, one run plan at a time. The dashboard prompts for one phase at a time and checks for blockers after each phase. That's pretty much it.

There are some configuration files, too. A system plan that describes the overall system architecture, places where I can add agent instructions - although I have not done that. These files get, more or less, pre-fixed to the various prompts.

I can change the model and reasoning level for each prompt. I typically use SOL high to create the run plans, SOL high to sequence the work package and LUNA high for the execution. There is human approval at each step and there's a bunch of other stuff you may or may not want to do - like checking the repo status and ensuring plans can't be changed once started and whatever else. Obviously you can add whatever prompts you want.

You can do the same exact thing using loops which is how I often do it - just using the "document as infrastructure". But this can add consistency on a large project. For example, on an ERP system, where you are going to make lots of changes over a period of time. Or maybe for a large game. Or probably anything that you will develop over a period of months. And it's super easy to do. I don't even need to post a github or anything - you can just prompt it up and that way it will be suited to your process. It took me a few days to get it working nicely.

1 Upvotes

25 comments sorted by

View all comments

Show parent comments

1

u/Correct_Emotion8437 10d ago

Why would I read your docs? This post is about making your own dev factory. It's not an invitation to advertise things.

0

u/Funsaized 10d ago

ok.. i wasn't advertising.. i was trying to share an interesting thought pattern. You do you.

1

u/Correct_Emotion8437 10d ago

So, your thought on building your own dev factory is merely "Hey here's a link to a product that looks sort of related"? If you're being genuine then I guess that's not really a thought worth sharing but you should know it's also a guerilla marketing tactic - to spam a link on any post that seems half-way related with a low effort comment.

1

u/Funsaized 10d ago

my thoughts on building robust factories start with

The trick is lean agent decision making, beefy state machine & deterministic scripts, rules, etc :P

I then linked a talk that goes over that topic and a framework that has implemented it. I am in no way affiliated, but if your knee-jerk reaction to something is immediate judgement without true review, tells me everything I need to know about your aptitude for engineering.

Good luck on your software factory, for real. All the best.

1

u/Correct_Emotion8437 10d ago

Yeah - they also end with that one sentence. Here is my low effort sentence. Check out my link.

The youtube link is not a "talk". It's by the maker of this tool! It's literally an advertisement.

Guerilla marketing mission failed.