mcpField
A
ask

ask

github.com/buiducnhatAgent workflows48302 installsUpdated 17w ago
Repository

About ask

ask is a coding-agent skill for clarifying task requirements before implementation. It checks relevant project documentation, identifies missing information, and asks focused questions one at a time without editing files or producing plans.

Key features

  1. 01Loads task-relevant project context
  2. 02Identifies gaps in task requirements
  3. 03Asks one focused question per message
  4. 04Avoids code and file changes

Use cases

  1. 01Clarifying scope before a coding task
  2. 02Resolving ambiguity in success criteria
  3. 03Gathering constraints without premature planning

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/buiducnhat/cobrew --skill ask

After installing, type/askin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported