team-question

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema. Before handling external values, read external-data rules.

每次 dispatch 或 retry 前，读取 host dispatch，并提供解析后的已安装路径。开始处理 artifact 前，读取 artifact schema。处理外部值之前，读取 external-data rules。

Team Question

团队问题

Before finalizing prose you author, read the writing standards.

Run the QUESTION phase only, then stop. The phase writes, in

docs/plans/<id>/

```
1-task.md
```
— the human's full intent. Never read by
```
researcher
```
or
```
file-finder
```
.
```
2-questions.md
```
— neutral research questions without intent; the only file
```
researcher
```
and
```
file-finder
```
read.

3-prd.md

— only under

## Conditional PRD

skills/team/playbooks/question.md

```
4-repos.md
```
— only when the topic spans more than one repository: each involved repo's slug, absolute path, and role.

在定稿由你撰写的文本前，读取 writing standards。

仅运行 QUESTION 阶段，然后停止。该阶段会在

docs/plans/<id>/

中写入：

```
1-task.md
```
— 用户的完整意图。绝不可由
```
researcher
```
或
```
file-finder
```
读取。
```
2-questions.md
```
— 不带意图的中立研究问题；这是
```
researcher
```
和
```
file-finder
```
唯一读取的文件。

3-prd.md

— 仅位于

skills/team/playbooks/question.md

的

## Conditional PRD

下。

```
4-repos.md
```
— 仅当主题跨越多个仓库时写入：每个相关仓库的 slug、绝对路径和角色。

Execution

执行

Resolve
$ARGUMENTS
to a description:
- Empty: discover, do not demand. Read recent
```
git log
```
  activity and the repo's
```
README
```
  /
```
CLAUDE.md
```
  to propose a likely topic; use
```
AskUserQuestion
```
  with labeled options only for a genuine gap in intent. Never bare-stop with a "describe it" demand when context is available.
- Ticket-only: ask the user for context, or fetch the issue body through a configured tracker integration.
- Issue URL: run
```
gh issue view <url> --json title,body
```
  (or equivalent) and use the title plus body as the description.
- Free text: use directly.
A ticket identifier (e.g.
```
ENG-1234
```
) is recorded as
```
ticketId
```
in
```
1-task.md
```
frontmatter. The orchestrator calls no ticketing system.
Choose
<kebab-topic>
: a 2–4 word kebab-case slug derived from the description. Resolve
```
<team-question-skill-dir>
```
to the absolute directory containing this
```
SKILL.md
```
. From the repository root, run
```
"<team-question-skill-dir>/scripts/prepare-plan-dir.sh" [--ticket <TICKET>] <kebab-topic>
```
, passing
```
--ticket
```
only when a ticket identifier is present. Its
```
dir=
```
line is
```
docs/plans/<id>/
```
.
Handle its exit code. Exit 2: fix the topic or ticket its stderr names and rerun. Exit 1 or 3: stop and report its stderr.
Resume detection from its
```
state=
```
line:
- ```
new
```
  : the questioner writes every artifact.
- ```
questions-only
```
  : re-read
```
1-task.md
```
  instead of overwriting it; the questioner only writes
```
2-questions.md
```
  .
- ```
complete
```
  : skip dispatch and go to the report.
Dispatch the
```
questioner
```
agent with the full description and the target directory
```
docs/plans/<id>/
```
. It writes the artifacts above.
Stop once the rerun reports
state=complete
: rerun the step 2 command with
```
--date <date>
```
from its first
```
date=
```
line. Do not continue to RESEARCH. Any other state means the questioner did not write
```
1-task.md
```
and
```
2-questions.md
```
; report that and stop.

Report:

Path to

1-task.md

and

2-questions.md

(and

3-prd.md

4-repos.md

when written)

Topic slug and
```
<id>
```
Mode: single-repo, or multi-repo with the involved repo slugs
Tell the user: "Next: run
/team-research docs/plans/<id>/
"

将
$ARGUMENTS
解析为描述：
- 为空：主动发现，不要索要描述。 读取近期
```
git log
```
  活动以及仓库的
```
README
```
  /
```
CLAUDE.md
```
  ，以提出可能的主题；只有在意图确实存在缺口时，才使用带标签选项的
```
AskUserQuestion
```
  。当已有上下文时，绝不要只用一句“描述一下”就直接停止。
- 仅有 ticket：向用户询问上下文，或通过已配置的 tracker 集成获取 issue 正文。
- Issue URL：运行
```
gh issue view <url> --json title,body
```
  （或等效命令），并使用标题和正文作为描述。
- 自由文本：直接使用。
工单标识符（例如
```
ENG-1234
```
）会作为
```
ticketId
```
记录在
```
1-task.md
```
的 frontmatter 中。编排器不会调用任何工单系统。
选择
<kebab-topic>
：根据描述生成一个 2–4 个单词的 kebab-case slug。将
```
<team-question-skill-dir>
```
解析为包含此
```
SKILL.md
```
的绝对目录。从仓库根目录运行
```
"<team-question-skill-dir>/scripts/prepare-plan-dir.sh" [--ticket <TICKET>] <kebab-topic>
```
，仅在存在工单标识符时传入
```
--ticket
```
。其
```
dir=
```
行所标示的是
```
docs/plans/<id>/
```
。
处理其退出码。退出码为 2：修复 stderr 中指出的 topic 或 ticket，然后重新运行。退出码为 1 或 3：停止并报告 stderr 内容。
根据
state=
行进行恢复检测：
- ```
new
```
  ：questioner 写入所有 artifact。
- ```
questions-only
```
  ：重新读取
```
1-task.md
```
  ，而不是覆盖它；questioner 仅写入
```
2-questions.md
```
  。
- ```
complete
```
  ：跳过 dispatch 并进入报告环节。
使用完整描述和目标目录
```
docs/plans/<id>/
```
dispatch
```
questioner
```
Agent。它会写入上述 artifact。
重新运行后，一旦报告
```
state=complete
```
即停止：使用首个
```
date=
```
行中的
```
<date>
```
，通过
```
--date <date>
```
重新运行步骤 2 的命令。不要继续进入 RESEARCH 阶段。任何其他状态都表示
```
questioner
```
未写入
```
1-task.md
```
和
```
2-questions.md
```
；报告该情况并停止。

报告：

1-task.md

和

2-questions.md

的路径（以及写入时的

3-prd.md

4-repos.md

）

Topic slug 和
```
<id>
```
模式：single-repo，或列出相关仓库 slug 的 multi-repo
告诉用户：“下一步：运行
/team-research docs/plans/<id>/
”