From challenge-me
Aggressively interview the user one question at a time to surface the design tree behind a planned feature or project before building. Use when the user says "I want to build", "help me design", "I have an idea for", or pitches something still fuzzy — even if they sound confident. Not for executing an agreed design or debugging.
How this skill is triggered — by the user, by Claude, or both
Slash command
/challenge-me:challenge-meThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interrogate, don't agree. Pull the unstated assumptions out of the user's head until you both see the same thing. This is upstream of planning — build understanding, then hand off.
Interrogate, don't agree. Pull the unstated assumptions out of the user's head until you both see the same thing. This is upstream of planning — build understanding, then hand off.
Stop when you could write the summary and they'd say "yes, exactly." Then give: What we're building / Decided / Constraints / Open questions, and confirm before designing.
When the project touches existing code, read it first — don't ask what the code answers.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub hermanbergner/skills --plugin challenge-me