ask
Structured clarification and requirements gathering through focused dialogue or with dry code. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
- Installs
- 302
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/buiducnhat/cobrew --skill ask- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ask automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Ask
Workflow
Step 1: Gather Project Context
Load only the project context relevant to the current task:
- If
docs/SUMMARY.mdexists, read it first. - Load only task-relevant detail docs.
- Prioritize
Code Standarddocs 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
FAQ
What does the ask skill do?
Structured clarification and requirements gathering through focused dialogue or with dry code. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
How do I install ask?
Run npx skills add https://github.com/buiducnhat/cobrew --skill ask in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ask/ (personal) or .claude/skills/ask/ (project).
Which AI agents can use ask?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ask safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ask?
It is published by buiducnhat in buiducnhat/cobrew. It has 302 recorded installs.
More from buiducnhat/cobrew
brainstorm
buiducnhat/cobrew
Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding.
execute-plan
buiducnhat/cobrew
Execute an approved implementation plan exactly and safely. Use for ExecPlan-style plan execution, resumable phase checklists, multi-hour implementation work, migrations, significant refactors, and plans that require verification checkpoints, status tracking, and final reporting.
write-plan
buiducnhat/cobrew
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use for ExecPlan-style work, multi-hour changes, significant refactors, migrations, resumable phase checklists, and work that should be handed off to execute-plan with clear validation.
docs
buiducnhat/cobrew
Create or refresh project documentation in docs/. Use when a project needs docs initialized or existing docs synced to the current codebase.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.