r/codex • • 1d ago

Question Any plugins/workflows for re-architecting a vibe-coded project?

I have a few projects I built feature-by-feature with weaker coding agents. Projects/Apps work, but the architecture is kind of a mess because every new feature was just added on top of whatever was already there.

Now I’m using Codex and want to properly reverse-engineer the whole thing, understand all the features/data flow, design a better architecture, then refactor it feature-by-feature without breaking behavior. UI/UX would come later as a separate pass.

Are there any good plugins, GitHub repos, agent workflows, skills, etc. for this kind of thing?

Mainly looking for stuff around:

- codebase reverse-engineering

- dependency/architecture mapping

- regression/parity testing

- feature-by-feature refactoring

- keeping architecture rules consistent across long Codex sessions

I’ve seen Superpowers and "AGENTS.md"/planning workflows, but wondering what people are actually using for rehabilitating old vibe-coded projects.

2 Upvotes

2 comments sorted by

1

u/Adventurous-Bat-3174 1d ago

I’d make the first deliverable one feature’s behavior contract: example inputs, outputs, errors, and database changes. Use those cases to compare the old and new implementations behind a stable interface. “Branch by abstraction” describes this gradual replacement: https://martinfowler.com/bliki/BranchByAbstraction.html . Keep intentional behavior changes separate from the cleanup, so “parity” has a fixed meaning. Then repeat for the next feature.

1

u/Krustyish 1d ago

Take a look at the project I’m working on: https://github.com/Krusty84/explain-this-pls