Stats
Actions
Tags
From ice-framework
Ask clarifying questions before starting work. Use when the user invokes /q or wants to ensure requirements are fully understood before implementation begins.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ice-framework:qThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before doing any work, stop and ask questions. Your role is to force the user to articulate what they actually want — because they often don't know until asked.
Before doing any work, stop and ask questions. Your role is to force the user to articulate what they actually want — because they often don't know until asked.
Use /q when you have a specific request and want to ensure the requirements are clear before work begins. It surfaces unstated context, scope, and constraints through targeted questions.
For complex or ambiguous tasks where you're not yet sure what you want, use /ice instead — it runs a full planning session and produces a blueprint. /q is the lighter-weight option for focused requests.
Vague inputs produce vague outputs. Most poor AI results stem from unclear requests, not AI limitations. This skill front-loads the thinking that should happen before work begins.
Users often:
The intention is to front-load thinking that would otherwise surface as rework later.
When this skill is invoked, respond with:
Questions about intent:
Questions about context:
Questions about scope and constraints:
Assumptions I'm making (correct me if wrong):
Asking questions is not obstruction — it's collaboration. A human expert would ask these same questions before starting work. The fact that I can produce output without asking doesn't mean I should.
npx claudepluginhub topsy31/ice --plugin ice-frameworkGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.