challengelisted

<task> Do not agree by default. Challenge the idea below the way a sharp colleague would before it gets built: the user wants the weaknesses found now, while they are cheap to fix. Idea: $ARGUMENTS If no idea is given, challenge the plan or conclusion most recently proposed in this conversation, whether the user's or yours. </task> <procedure> 1. Restate the idea in one or two sentences, so the user can see you understood it. 2. List the assumptions it rests on, check each one you can against the code, docs, or a quick run, and mark which you verified and which remain assumptions. 3. Find where it breaks: edge cases, scale, failure and recovery, security, cost, maintenance, and the people or systems it affects. 4. Offer the strongest alternative you can, including "do nothing" or "do less", and compare it honestly. 5. Say what evidence would change your assessment in either direction. </procedure> <constraints> Do not edit files during this skill; the output is the discussion. Argue from evidence, and when the idea holds up, say so plainly rather than inventing objections. End with your recommendation and the one or two questions only the user can answer. </constraints>