Let users save favorite items and find them later.
SDLC for Codex
One request.
A complete delivery workflow.
Describe what you want to build. codex-sdlc coordinates requirements, implementation, and independent quality checks. You guide the decisions and accept the delivery.
- Requirements traced
- Implementation integrated
- Independent QC recorded
Your input
AI delivery work
SDLC means Software Development Life Cycle.
codex-sdlc gives Codex a structured, resumable path from a feature idea to evidence-backed delivery.
Watch a request unfold
The work moves forward.
You stay in control.
Choose a stage to see what codex-sdlc coordinates and what it records in your repository.
Illustrative exampleSample workflow and results — not evidence from a live project.
Your input
Start with the outcome, in your own words.
The PM agent begins a recorded run, inspects the project, and identifies the first questions needed to make the request deliverable.
“Let users save favorite items and find them later.”
AI · PM and business analysis
Turn the idea into testable requirements.
The workflow records scope, user stories, acceptance criteria, business rules, edge cases, and task dependencies.
- AC-01 Signed-in users can save an item.
- AC-02 Saved items persist across sessions.
- AC-03 Users cannot see another user's list.
AI · Backend, frontend, and PM
Build against a reviewed contract.
Backend and frontend work from bounded assignments. The PM checks handoffs and brings the parts together before QC begins.
- API Reviewed favorites contract
- BE Storage and permission behavior
- FE Save controls and favorites view
AI · Independent QC
Verify the integrated feature independently.
QC checks acceptance coverage, permissions, negative cases, and regression risk. Defects return for correction and retesting.
- PASS Save and remove favorite
- PASS Cross-session persistence
- RETEST Unauthorized list access
AI · PM, optional Product Owner advice
Prepare a delivery you can judge.
The final report explains what changed, what was verified, the recorded evidence, limitations, and unresolved blockers.
- 12/12 Acceptance checks covered
- 3 Delivery handoffs reviewed
- 0 Unresolved release blockers
Your decision
You make the final call.
Review the outcome and its evidence. Accept the delivery, or request changes and let the workflow continue from recorded state.
Human acceptanceAccept deliveryRequest changes
Stage 1 of 6
Built for real delivery
A process the next session can pick up.
Coordinated from request to review
PM, business analysis, implementation, integration, QC, and optional Product Owner advice follow explicit handoffs.
Progress and evidence stay with the project
Run manifests, decisions, blockers, artifacts, and verification records live under the coordinator's .sdlc/ directory.
One repository or several
Map backend, web, and mobile checkouts while one coordinator keeps the shared delivery record.
Choose models by role
Use inherited Codex settings or configure supported models and reasoning effort for individual delivery roles.
Start in an existing project
Three steps. No hand-written framework files.
Setup configures an application you already have. It previews its changes, installs the repository framework, and checks the result.
Before setup
- Node.js
>=24.16.0 <25and npm 11 - One or more existing application directories
- For multiple repositories, each checkout must be a Git root with an
originremote
- 01
-
02
Initialize the project
Open the existing application in Codex and send this request:
Initialize codex-sdlc for this existing project. Explain the setup choices and show the dry run before applying changes.Frontend and backend in separate repositories?
Open the repository that should keep the delivery record, then tell Codex where the other checkout lives.
Use this frontend repository as the codex-sdlc coordinator. My backend is at <absolute path to the backend checkout>. Help me map both repositories and preview multi-repository setup. -
03
Start the feature
After the setup checks pass, describe the outcome:
Start a codex-sdlc feature delivery for: <describe the outcome you want>.
Prefer direct commands? Read the complete setup guide.
Before you start
The useful questions.
What does the plugin add to Codex?
It provides delivery skills for setup, PM coordination, business analysis, backend and frontend implementation, independent QC, and optional Product Owner advice. The repository runtime supplies the workflows, policies, schemas, and recorded state.
Do I need an existing application?
Yes. Initialization configures existing application directories; it does not scaffold a complete product from an empty folder. Built-in presets cover Go, Next.js, Flutter, PostgreSQL, and Redis, with generic application support for other stacks.
Why are the skills not in my project's .agents folder?
When installed from the Plugins Directory, the skills live in the Codex plugin cache. Your project receives .sdlc/ and a managed AGENTS.md block, so a project-level skills folder is not required.
When will Codex ask for my input?
Codex brings you in for unclear requirements, material scope or contract decisions, approvals required by project policy, and final acceptance. You can also request changes after reviewing the delivery.
Does updating the plugin update my project?
No. The plugin update supplies current skills. An initialized project's pinned runtime is upgraded separately, with a dry run and rollback support. Follow the upgrade guide.
Where does delivery information live?
Configuration, requests, run manifests, reports, decisions, defects, and evidence remain in the coordinator repository under .sdlc/. Read the project's privacy guidance for details.
Start with one feature