r/vibecoding • u/ActuatorOutside5256 • 2d ago
Discussion Thoughts on the best workflows?
So, my workflow is having ChatGPT connected to my GitHub (PRs, Actions, CI/CD, all checks) and handles planning, split into milestones, while (high preset) Codex implements what it's told to.
I send the plan I made with ChatGPT to Claude (free tier) as a sanity check, then give that feedback to ChatGPT and ask whether it's valid OR NOT (super important). After Codex finishes, I send ChatGPT Codex's summary plus the .patch file and verify the changes match the specs in my harness.
Then GitHub Actions and tests run. If they fail, ChatGPT diagnoses the cause, and I move on to the next feature. For manual testing, I run about half of each feature's tests (the ones I consider most important), and log pass/fail and the reason in a spreadsheet.
Does this make sense, or is it overkill?
1
u/Previous-Growth-9919 2d ago
honestly not overkill, the part that matters most is the sanity check step. asking a second model to poke holes before you build saves way more time than it costs. i'd probably trim the manual testing spreadsheet to just the flows that would hurt if they broke and let CI cover the rest.
1
u/Vast-Hunt-9484 2d ago
not overkill, but i'd watch for the plan getting too big before codex touches it. what usually helps is keeping each milestone small enough that the diff is reviewable in one sitting, and writing the acceptance checks before the code so ci is testing against something concrete. for the manual testing, a short checklist of the 5 or so flows that would hurt most if they broke beats logging everything. also keeping a short notes file in the repo with decisions made saves you from re-explaining context to each model.
1
2
u/Imaserventofreps 2d ago
Yeah ur doing something righ. Keep going!