grill-me

Resolve under-specified software migration plans by interrogating open design decisions one at a time. The grilling process waits for your answer at each branch and provides recommended responses until every decision is settled, preventing expensive build failures.

Reviewing a software design decision tree is best handled by sequentially interrogating each open branch. The process asks one question at a time, reads the codebase for discoverable answers, and outputs a final summary of resolved and deferred decisions.

Yes, you can use codebase reasoning to clarify open decisions during pre-implementation planning. When answers are discoverable in the code, the codebase is read directly as the source of truth to resolve design branches without relying solely on manual input.

Force design decisions for a non-trivial schema change by triggering a sequential question and answer flow. The interrogation continues branch-by-branch, offering recommended answers with brief reasons, until all open decisions are resolved and a plan solidifies.

You need decision tree interrogation for a refactor plan when the design is under-specified and you must force open decisions before moving forward. It is specifically for non-trivial refactors where unresolved branches could cause expensive build failures.

After interrogating all open design decisions, you get a closing artifact containing a short bullet list. This summary includes all resolved decisions alongside an open or deferred list, establishing shared understanding before implementation begins.