sanity-check

Verification of assumptions prevents incorrect solutions by forcing explicit checks before proposing changes. List each key assumption about the problem, then directly confirm it through code inspection, log review, or reproduction. Stop and reassess if any critical assumption cannot be verified.

Assumption cascades compound when unverified premises lead to wrong solutions. Before proposing a fix, catalog assumptions explicitly, verify their validity through direct checks, and halt progress if verification fails. This risk mitigation step catches root causes early.

Validate assumptions before implementing changes across code understanding, debugging, and architectural decisions. Verification steps confirm existence, behavior, and root cause. This is essential in risk-management workflows where incorrect assumptions cascade into flawed solutions.

Yes. Assumption verification applies across debugging, code understanding, and architectural decisions. By explicitly listing premises and requiring verification steps before proposing changes, you ensure architectural choices rest on confirmed facts rather than unexamined assumptions.

If verification fails, the Skill halts progress and prompts reassessment. This safe stop prevents implementation of solutions built on unverified premises, reducing risk and ensuring you understand the actual problem before coding changes.