Vibe Thinking - The PM Who Writes Requirements That an AI Can Actually Use

The de team is moving fast. Requirements come in, developers build quickly, and then the happens. The outcome isn’t what was wanted. The brief was technically correct but the result was wrong. The team assumed shared context that was never written down. Nobody asks for specifications now; you just prompt the AI and go. And that’s exactly the problem. Every org I’ve spoken with that has rolled out AI coding tools has had some version of this moment. Vibe coding built the wrong thing fast. The error happened upstream in the brief.