---

name: rethink description: "Use when the user wants a proposal or approach reconsidered from first principles, or when evidence shows the current design is weak." user-invocable: true

Rethink

Rebuild the proposal from the required outcome and verified real-world constraints. Identify assumptions, remove those that evidence does not support, and test the remaining constraints against concrete cases.

Compare genuinely different approaches. State each approach's costs, failure modes, reversibility, and proof needs. Use development-skills:best-practices when current external evidence can change the choice.

Recommend the simplest consistent design that meets the outcome. Explain why it is better than the current proposal and what evidence would overturn the recommendation. Return the result to the active development workflow before implementation.