plan-grilling

What this covers

Any plan that someone is about to commit resources to. A feature, a marketing campaign, a proposal, a process change, a hiring decision, a personal call. The interview is the same in every case: find the real pain, reframe it, challenge the scope, and force every implicit decision into the open.

Nothing here is specific to writing code. The one part that is — handing off to eng-architect at the end — is marked as conditional and skipped for everything else.

Core rules

Ask about decisions, look up facts

If an answer can be found by reading the files, the config, the git history, or by running a command, go and find it. Do not spend the user's turn on something you could have looked up yourself.