Back to Details

as-ask

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Ask

提问

Purpose

用途

Gather the information needed to proceed with a task through structured, focused dialogue.
This skill is for asking only. Do not plan, implement, or produce any artifacts.
通过结构化、聚焦的对话收集推进任务所需的信息。
本技能仅用于提问，请勿进行规划、实现或产出任何交付物。

Scope Gate (Required Before Starting)

适用前提（启动前必须满足）

Use this skill only when:
  1. The task is underspecified — key requirements, constraints, or decisions are missing
  2. User input is required — the task cannot proceed without answers from the user
  3. No assumptions are safe — guessing would risk wasted effort or wrong direction
If the task is clear enough to act on, use 
brainstorm
, 
write-plan
, or 
quick-implement
instead.
仅当满足以下条件时使用本技能：
  1. 任务说明不充分 —— 缺失核心需求、约束条件或决策信息
  2. 需要用户输入 —— 没有用户答复则无法推进任务
  3. 无法做出安全假设 —— 自行猜测可能导致无用功或方向错误
如果任务足够清晰可直接执行，请使用
brainstorm
、
write-plan
或
quick-implement
。

Workflow

工作流

Step 1: Gather Project Context

步骤1：收集项目上下文

Load project context per the shared Context Loading Protocol. Only gather what is relevant to the current task. Skip if no docs exist.
按照共享的上下文加载协议加载项目上下文，仅收集与当前任务相关的内容，无相关文档可跳过。

Step 2: Identify Information Gaps

步骤2：识别信息缺口

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
明确任务推进前具体缺失的信息：
  • 目标与用户价值
  • 范围边界与非目标项
  • 约束条件（技术、UX、性能、时间线）
  • 成功标准
  • 存在多个有效选项的关键决策点

Step 3: Ask Questions (One at a Time)

步骤3：提问（一次一个问题）

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
依次提出针对性问题填补每个信息缺口。
规则：
  • 每条消息仅提一个问题
  • 可行时优先使用选择题选项（2-4个选项）
  • 仅当无合理选项时使用开放式问题
  • 不要询问项目文档中已有答案的问题
  • 不要过早询问实现细节
  • 不要在一条消息中捆绑多个问题

Step 4: Confirm and Hand Off

步骤4：确认与交接

Once all gaps are closed:
  1. Summarize the collected answers concisely
  2. Confirm with the user that the summary is correct
  3. Recommend the appropriate next skill based on complexity:
    • Simple, clear task → 
      quick-implement
    • Complex or risky task → 
      write-plan
    • Ambiguous, high-risk, or exploratory → 
      brainstorm
所有信息缺口填补完成后：
  1. 简要总结收集到的答复
  2. 向用户确认总结内容是否正确
  3. 根据复杂度推荐合适的下一步技能：
    • 简单清晰的任务 → 
      quick-implement
    • 复杂或高风险任务 → 
      write-plan
    • 模糊、高风险或探索性任务 → 
      brainstorm

Rules

规则

  • Do not write code or modify any files
  • 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
  • Feeds into: 
    brainstorm
    , 
    write-plan
    , 
    quick-implement
  • 不要编写代码或修改任何文件
  • 不要产出计划、设计或实现类交付物
  • 不要做假设，以提问替代猜测
  • 保持问题简短聚焦
  • 遵循YAGNI原则：仅询问推进任务严格必需的信息
  • 可衔接技能：
    brainstorm
    、
    write-plan
    、
    quick-implement