skill-pressure-test

Have the plan interrogated one question at a time, with each question carrying a recommended answer you can confirm or dispute. The process follows decision dependencies, surfaces contradictions, and ends with a verdict of sound, sound-with-changes, or unsound.

Brainstorming opens a space up and generates options, while pressure-testing closes one down and looks for what is wrong with an existing position. Use pressure-testing only when a plan already exists and the risk is an unspoken flaw.

Skip it when you need options generated, when no position exists yet, or when the answer is discoverable by reading the codebase. It also stops early if the plan proves sound or if an answer invalidates the entire premise.

Batched questions get shallow, questionnaire-style answers shaped by whichever item the reader cares about. A single answered question changes what the next question should be, producing deeper and more accurate resolution.

It produces a verdict on where the plan stands, the decisions settled in order, changes the answers caused, questions still open with what they block, and facts found with their sources cited.