Built in Replit, Lovable or Base44 and never used Claude Code or Cursor? Level up once before you level up with us: put your app on GitHub and set up Claude Code, step by step →
What changes when you work inside a process
Vibe coding is good at one thing, and it is a real thing: getting from an idea to a working demo before the idea goes cold. A lot of good products started that way. Nobody here is going to tell you to stop.
Production asks for something else. Not more talent. Habits. Four of them do most of the work:
- 01Ask what “done” means. Before the first prompt, not after the demo.
- 02Prove it. A test that fails without your change and passes with it.
- 03Let someone else look. Whoever built it is the worst judge of it. That includes the agent.
- 04Know what you shipped. What changed, who checked it, and how to take it back.
Nobody picks these up from a blog post, this one included. You pick them up by being stopped, politely, every time you skip one. That is all a gate is. Inside the SDLC the habits are the default path: the easy way through is the right way, and the shortcut is not there to take.
The skill tree
Ten skills over four levels. Each one is a step or a gate in the SDLC, and each one teaches a single question. You unlock them by doing the work.
-
LV1
Vibe coder
You prompt. It works on your machine.
- You can
- Get from an idea to a working demo, fast.
- Training wheels
- All on. The agents write the criteria, plan the change and ask you the questions you did not know to ask.
Prompt start
You learn to describe what you want.
“Does it run?”
-
LV2
Builder
Stories with criteria. Tests exist.
- You can
- Write a story someone else could build, and prove it with tests.
- Training wheels
- You read the agent’s refinement questions before you approve, and start guessing them before it asks.
Refinement gate
Product thinking. Acceptance criteria.
“What does done mean, and how would we know?”
Preflight gate
Planning your change before you make it.
“What will this touch, and what could it break?”
Verify gate
Testing.
“Prove it.”
-
LV3
Engineer
Reviews, audits, gates pass. Readiness 3 and up.
- You can
- Ship changes that get through three reviewers without a round trip, most of the time.
- Training wheels
- You answer the refinement questions yourself, before the agent does. A rejection is something you read, not something you rerun.
Three reviewers gate
Code review. Reading your own diff.
“Would I approve this if someone else wrote it?”
Audit gate
Quality and consistency.
“Does this still look like one codebase?”
Decision register step
Telling a business decision from a technical one.
“Is this mine to decide, or theirs?”
Retro step
Estimating, and getting better at it.
“Why did that take twice as long as I said?”
-
LV4
Forward-deployed engineer
Readiness 4 out of 5.
- You can
- Take a client’s app to production and explain every decision in it, to the person who owns it.
- Training wheels
- Off. The gates stay, because senior engineers keep gates too. You just stop needing them to tell you why.
Due diligence step
Architecture, security, data.
“What would an investor’s engineer find first?”
Load test step
Performance and capacity.
“What happens at ten times today’s traffic?”
Release & rollback step
Operations.
“If this goes wrong at 2 a.m., how do we undo it?”
Sprint 1 vs. sprint 5
The same person, the same kind of story, four sprints apart. Nothing about the process got easier. The person did.
> refine S-04 export invoices
AGENT Before this can start:
? Who may export: admins, or everyone?
? What happens with 50,000 rows?
? How would we know it works?
GATE refinementREFUSED
AGENT Criteria drafted. Approve?
> yes
VERIFY 2 of 5 untestedREWORK
REVIEW securityREWORK
another tenant’s invoices in the file
REVIEW architectureREWORK
REVIEW functionalAPPROVE
AUDIT 3 findingsREWORK
> refine S-31 export payouts
YOU 5 criteria, 2 edge cases.
out of scope: PDF. admins only.
AGENT 1 question: export retention.
business call: filed as D-12
GATE refinementPASS
YOU preflight: 3 filesPASS
VERIFY 5 of 5 coveredPASS
REVIEW securityAPPROVE
REVIEW architectureAPPROVE
REVIEW functionalAPPROVE
AUDIT 0 findingsPASS
Illustrative. Two sessions written to show the difference, not a recording of a real project.
What is a forward-deployed engineer?
Some software is too particular to install and walk away from. So the company that sells it sends an engineer to the customer, forward, into the customer’s own reality, to make the product work there. That person is a forward-deployed engineer.
- Owns the problem end to end. Not a ticket. The problem.
- Talks to the business. In its language, about its decisions.
- Ships to production. Not to a demo, not to staging.
- Stands behind it. Next week, when something breaks, it is still theirs.
The bar
That is the bar the 
prodready SDLC is built to: an app you could hand to a client tomorrow, and answer every question they ask about it.
For teams
Agencies and founders onboarding juniors.
A junior with a coding agent produces a lot of code, quickly, and nobody senior has the time to read all of it. That is the usual problem, and more seniors is the usual answer.
Put the same junior inside the SDLC and the process does the part a senior would do first: it refuses a story nobody refined, asks for proof, sends every change to three reviewers who did not build it, and audits the sprint. The work that comes out is work a senior can sign off. The junior finds out why along the way, one gate at a time.
- For an agency: one process for every developer and every client, and a record of who checked what.
- For a founder: your first hire works to the same bar on day one as in month six.
- For the junior: a senior’s questions, asked every time, without waiting for a senior.
The learning shows. You can see it on the dashboard’s Analytics page: rework rate, how often verify failed before it passed, how consistent the estimates were and how each gate went, sprint by sprint. Which way those lines go is up to the person doing the work.
Find out where you start.
The free due diligence scores the app you have today. That is your first reading. Then run the SDLC and watch it move.