The PM vibe coding scenario described here cuts to the heart of a real accountability problem: when the person shipping code doesn't understand it, can't debug it, and won't be around when it breaks in production, who's responsible?

This isn't just a PM problem — it's the same dynamic playing out at every seniority level with AI-assisted coding. The speed feels real, but the ownership gets blurry.

A few of us have been working on formalizing exactly this challenge: the Agile Vibe Coding Manifesto (https://agilevibecoding.org). It builds on the original Agile Manifesto to address environments where AI is generating significant amounts of code, and its second principle is simply "Humans remain accountable for software systems — regardless of how code is produced."

The manifesto doesn't argue against AI-assisted development. It argues that speed of generation has to be matched by clarity of intent, traceability of decisions, and genuine human accountability for what gets deployed. Whether you're a PM shipping a quick tool or a senior engineer steering an agent, the accountability question doesn't go away.