decision-challenge — doubt with a stopping rule

Use this immediately before a consequential commitment: an irreversible migration, a production-auth change, a costly architecture bet, a launch exception, or a plan whose confidence is higher than its evidence. The purpose is to find the decision-changing doubt, not to perform scepticism forever.

This skill is read-only unless the user also asks to change the artifact. It emits a challenge record and a verdict. Finished code review stays with ../review/SKILL.md or ../code-review/SKILL.md; consistency across constitution/spec/plan/tasks stays with ../analyze/SKILL.md.

One bounded cycle

MATERIALIZE → ISOLATE → ATTACK → TEST → RECONCILE → VERDICT

1. MATERIALIZE the decision

Do not challenge a cloud of conversation. Write the concrete packet: