elicit

Second-pass reasoning applies methods like pre-mortem, inversion, and red team analysis to your generated artifacts, challenging assumptions and revealing risks to produce actionable findings with a delta of changes.

Second-pass reasoning is needed for high-stakes decisions or project forks, applying rigorous critique to specs, designs, plans, or code to reveal trade-offs and alternative approaches before committing.

Apply pre-mortem analysis by directly invoking the method to run a rigorous second pass on your latest strategic plan, generating concrete recommendations and open questions to guide next steps.

First principles reasoning can critique software architecture designs by breaking down assumptions during the second pass, producing a clear delta of findings that reveals trade-offs and alternative approaches.

The best way to challenge assumptions is applying structured reasoning methods like Socratic questioning or stakeholder mapping, which rigorously evaluate strategic artifacts and output a delta of concrete recommendations.

Second-order effects analysis works for operational plans by evaluating downstream consequences during the structured second pass, maintaining an explicit default workflow for iteration to surface hidden risks.