Skill

ask

Structured clarification and requirements gathering through focused dialogue or dry code. Asks one question at a time when tasks are ambiguous or underspecified.

developer-tools

npx claudepluginhub buiducnhat/cobrew --plugin cobrew

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/cobrew:ask [question]

User invocable

Model invocable

Inline context

Default effort

Argument hint[question]

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Load only the project context relevant to the current task:

SKILL.md

53 lines · ~458 tokens

Similar Skills

clarification

Clarifies vague user requests via iterative Q&A loop and parallel subagent codebase exploration. Outputs scoped context brief for precise planning. Triggers on 'I want to...' or ambiguous scopes.

engineering-discipline

ask-questions-if-underspecified

Asks minimal clarifying questions to resolve underspecified requirements like objectives, scope, constraints, and acceptance criteria before implementing. Invoke explicitly via /ask-questions-if-underspecified.

base-config

ask-questions-if-underspecified

5.3k

Asks targeted clarifying questions when requests lack clear objectives, scope, constraints, environment, or acceptance criteria before implementing.

ask-questions-if-underspecified

Stats

LanguageHTML

Parent stars47

Parent forks3

MaintenanceExcellent

Last CommitMay 18, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Ask

Workflow

Step 1: Gather Project Context

Load only the project context relevant to the current task:

If docs/SUMMARY.md exists, read it first.

Load only task-relevant detail docs.

Prioritize Code Standard docs for implementation conventions.

If docs conflict with code or user intent, use the available input/question before broad changes.

Skip this step if no project docs or useful repository files exist.

Step 2: Identify Information Gaps

Determine exactly what is missing before a task can proceed:

Objective and user value

Scope boundaries and non-goals

Constraints (technical, UX, performance, timeline)

Success criteria

Key decisions with multiple valid options

Step 3: Ask Questions (One at a Time)

Ask targeted questions sequentially to close each gap.

Rules:

Ask exactly one question per message

Prefer multiple-choice options when practical (2–4 choices)

Use open-ended questions only when no reasonable options exist

Do not ask questions already answered by project documentation

Do not ask about implementation details prematurely

Do not bundle multiple questions into one message

Rules

Do not write code or modify any files, only support dry coding into output, not into artifacts

Do not produce plans, designs, or implementation artifacts

Do not make assumptions; ask instead

Keep questions short and focused

Apply YAGNI: only ask what is strictly necessary to proceed

Ask

Workflow

Step 1: Gather Project Context

Load only the project context relevant to the current task:

If docs/SUMMARY.md exists, read it first.
Load only task-relevant detail docs.
Prioritize Code Standard docs for implementation conventions.
If docs conflict with code or user intent, use the available input/question before broad changes.

Skip this step if no project docs or useful repository files exist.

Step 2: Identify Information Gaps

Determine exactly what is missing before a task can proceed:

Objective and user value
Scope boundaries and non-goals
Constraints (technical, UX, performance, timeline)
Success criteria
Key decisions with multiple valid options

Step 3: Ask Questions (One at a Time)

Ask targeted questions sequentially to close each gap.

Rules:

Ask exactly one question per message
Prefer multiple-choice options when practical (2–4 choices)
Use open-ended questions only when no reasonable options exist
Do not ask questions already answered by project documentation
Do not ask about implementation details prematurely
Do not bundle multiple questions into one message

Rules

Do not write code or modify any files, only support dry coding into output, not into artifacts
Do not produce plans, designs, or implementation artifacts
Do not make assumptions; ask instead
Keep questions short and focused
Apply YAGNI: only ask what is strictly necessary to proceed