Speed without direction is just noise. To prevent my AI sessions from spiraling into chaos, I enforce a strict “Layered Decision” protocol.
Layer 1: The Big Picture (No Code Allowed)
We agree on the architecture and data flow first. If the AI tries to suggest folder structures or specific implementation, I stop it: “Stick to the system design. Don’t make code changes until we have finalized the plan.”
Layer 2: The “Immutable” Log
In the heat of an AI conversation, it’s easy to lose track of what you agreed on.
My Rule: Every decision goes immediately into a separate decisions.md file.
Why: No re-litigating. If it’s not in the log, it didn’t happen.
The Result: We moved from “abstract idea” to “10-phase implementation plan” without getting bogged down in syntax errors or folder trees.
The Takeaway: You cannot let the AI drive the abstraction level. As the Senior Engineer, you set the altitude. The moment you drop into the weeds too early, you lose the project.
How do you keep your technical planning sessions focused? Do you have a “No Code” rule for the first hour?
Originally posted on LinkedIn