We’ll explore the emerging “vibe coding” phenomenon - where developers collaborate with AI to generate code through natural language prompts rather than manual programming. First introduced by Andrej Karpathy in 2025, this approach transforms the developer’s role from writing code to guiding, testing, and refining AI-generated solutions. But what would “vibe requirements engineering” look like? We’ll examine whether a similar conversational, AI-assisted approach could revolutionize how we gather, document, and validate requirements. Can we simply “vibe” with AI to produce comprehensive requirement specifications? Join us to discuss the potential benefits, limitations, and ethical considerations of bringing this potential new method to RE—and whether it represents the future of our discipline or risks undermining its methodological foundations.

I have been self-employed in software development for nearly 20 years now and have already written thousands of pages of requirements. In doing so, I’ve noticed how much better offers function when they don’t just cover the bare minimum and are 2-3 pages long, but instead detail everything, and how much easier everyone involved finds the progress of the project becomes, as it is easier to follow the status. As a result of a huge project that was awarded to someone else who sold cheaply and then bungled the work, I’ve made it my task to make software offers comparable, to make such situations less common, and in Andreas and Angelika, I’ve found motivated allies.