A PM’s Guide to Vibe-Coding with AI
Zusammenfassung
Pixel shares a practical guide to vibe-coding, showing how clear requirements can turn an AI coding assistant into a useful tool. The example is a meeting room booking system, with rules for access, booking windows, conflicts, and cancellations—and a reminder to catch rules the AI invents.
DEV Community
A PM's Guide to Vibe-Coding: Requirements First, Code Second
For about a year, my team kept a shared resource — meeting rooms — in a spreadsheet and a group chat. Someone would write "Room B, Thursday 2–4pm?" in the chat. Someone else would check the spreadsheet. Someone would forget to update it. And then two teams would show up at the same door at the same time, each holding a laptop and a reasonable claim to the room. It worked badly, and everyone knew it worked badly. Nobody had time to build a real system for it. And I am a project manager, not a programmer — I hadn't written production code in years. So I did the thing every PM seems to be doing now: I asked an AI coding assistant to build it for me. I want to be honest about what happened next. The AI did not magically turn my idea into software. It turned my requirements into software — and the difference between those two sentences is the whole story. The requirements came first Before I opened the editor, I spent a day writing the rules. Not a PRD, not a forty-page spec — just a list, in plain language, of how the thing had to behave. Four questions did most of the work: Who can use it? Anyone on the team, no approval needed. If a tool needs a gatekeeper, people go back to the group chat. When can they book? Within a fixed window ahead of time — far enough to plan, short enough that nobody hoards rooms weeks out. What happens when two people want the same slot? The second booking fails, clearly, in words a human understands. No silent overwrites, ever. What happens when someone cancels? The slot frees up immediately, and the system shows it as free. No ghost bookings. Those four answers became the spine of everything I asked the AI to build. Everything else — the layout, the colours, the buttons — was decoration. Here is the part nobody warns you about: the AI will also invent rules. Mine did, on the first day. It added an auto-expiry rule I never asked for — unconfirmed bookings would vanish after two hours. It sounded sensible. It was also completely made up, and it would have deleted real bookings made by real people who simply hadn't clicked a confirmation nobody told them about. So I learned the first real lesson of vibe-coding, and it is a PM lesson, not a coding lesson: every rule in the system must come from your written spec. If a behaviour isn't in the list, it doesn't exist. I added one line to the top of my spec, and it stayed there for the whole build: "Build only the rules written here. Do not add rules of your own." The rules I insisted on, the ones the AI would never have written by itself, were the boring human ones: One active booking per person per day. Not because the system needs it, but because without it, one organised person books every room and everyone else goes back to the spreadsheet. Every booking shows a name. Not an ID, not an email — a name. When two people collide, they need to know who to talk to. Software can't resolve that conversation; it can only make it possible. The system never moves or deletes a booking silently. If something changes, the person affected gets told. This rule cost me an afternoon of argument with the AI, which kept trying to "helpfully" resolve conflicts on its own. I kept deleting that help. Those three rules are the whole difference between a tool people trust and a tool people route around. The AI was very good at the first kind of rule — the logic. It was blind to the second kind — the trust. That part was my job, and no prompt would have done it for me. The workflow: small prompts, real acceptance tests The tools were deliberately boring: an AI coding assistant in my editor, plain HTML, CSS and JavaScript with no framework, a private repo for version control, and Cloudflare Pages for hosting. Nothing exotic. The point of the exercise was the method, not the stack. I wrote prompts the way I write tickets: context first, then the rule, then what "done" looks like — one feature at a time. I never asked for the whole app at once. Every prompt ended with the same ac...

Powered by Readybot.io