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:

The task is underspecified — key requirements, constraints, or decisions are missing
User input is required — the task cannot proceed without answers from the user
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.

仅在以下情况下使用此技能：

任务描述不明确——关键需求、约束条件或决策信息缺失
需要用户输入——没有用户的回答，任务无法推进
无法安全假设——猜测会导致精力浪费或方向错误

如果任务足够清晰可执行，请改用

brainstorm

、

write-plan

或

quick-implement

技能。

Workflow

工作流程

Step 1: Gather Project Context

步骤1：收集项目上下文

Before asking questions, read available project documentation to avoid asking things already answered:

```
docs/project-pdr.md
```
```
docs/architecture.md
```
```
docs/codebase.md
```
```
docs/code-standard.md
```

Only gather what is relevant to the current task. Skip if no docs exist.

提问前，请阅读现有项目文档，避免询问已有答案的问题：

```
docs/project-pdr.md
```
```
docs/architecture.md
```
```
docs/codebase.md
```
```
docs/code-standard.md
```

仅收集与当前任务相关的信息。若无相关文档可跳过此步骤。

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:

Summarize the collected answers concisely
Confirm with the user that the summary is correct
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
```

填补所有信息缺口后：

简洁总结收集到的答案
与用户确认总结内容正确无误
根据复杂度推荐合适的后续技能：
- 简单、清晰的任务 →
```
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

请勿编写代码或修改任何文件
请勿生成计划、设计或实施工件
请勿假设，有疑问就提问
保持问题简短且聚焦
应用YAGNI原则：仅询问推进任务绝对必要的信息

Integration

集成

Feeds into:
```
brainstorm
```
,
```
write-plan
```
,
```
quick-implement
```
Use
```
brainstorm
```
when exploration and design framing are needed after gathering requirements
Use
```
write-plan
```
when requirements are clear and a structured plan is needed
Use
```
quick-implement
```
when the task is small and well-defined after gathering requirements

输出对接至：
```
brainstorm
```
、
```
write-plan
```
、
```
quick-implement
```
收集需求后，若需要探索和设计框架，请使用
```
brainstorm
```
若需求明确且需要结构化计划，请使用
```
write-plan
```
若任务小且定义明确，请使用
```
quick-implement
```