This is Kai, the creator of codex-sdlc. I am offering you a chance not to spend as much time as I do on the coordination details of the AI coding process - specifying requirements, passing work between the backend and frontend, tracking down open issues and resolving if the implemented solution meets the initial request.

\---

I've created a reusable workflow for Codex that begins with a natural language feature request. A project manager role runs through:

\- business analysis (requirements + acceptance criteria)

\- backend (API contracts + implementation + database changes)

\- frontend (web + mobile implementation)

\- independent AI quality assurance (comparison of the integrated result with the requirements)

\- delivery report (evidence and outstanding limitations for your review)

You are engaged throughout the process at points of clarification or when major decisions must be made, and you make the final judgment about acceptance. Subsequent progress is saved in the project's \`.sdlc/\` directory for continuation at a later time. You can map separate backend, web, and mobile repositories and set up AI models by role.

https://reddit.com/link/1wo09fr/video/xfzekd05e8rh1/player

\---

The walkthrough

I created a 50-second simulated walkthrough using this example:

"Let users save favorite items and find them later."

This shows how a request moves through the system from requirements to backend, web/mobile previews, quality checks and human acceptance. The interface and test results you see in the video are illustrative - this is not a recording of an actual delivery run, nor am I suggesting that a feature takes 50 seconds to build.

https://reddit.com/link/1wo09fr/video/oaaruyr0e8rh1/player

\---

How to try it

1. Visit [https://kaiz.cloud](https://kaiz.cloud) and follow the Codex plugin installation link.

2. Open an existing project in Codex.

3. Ask: "Initialize codex-sdlc for this project and show me the setup preview."

4. Review the proposed setup and apply it.

5. Let's start small: “Start a codex-sdlc feature delivery for: \[describe your feature\].”

Setup configures the framework for an existing application. It will not scaffold an entire application from an empty folder.

\---

The framework is free and open source. Codex access and usage are separate.

Source: [https://github.com/prime-vimihi/codex-sdlc](https://github.com/prime-vimihi/codex-sdlc)

\---

I'd appreciate any feedback from people who tried it out for themselves on their own projects. Where does the structure help, and where does it create unnecessary overhead? I'm especially interested in setup friction and manual handoffs that still need to happen.

I created codex-sdlc: an open-source Codex plugin that orchestrates requirements, implementations, and quality checks