prd-discovery

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use this skill to interview the user and produce a clear PRD for Ralph execution.

使用此技能与用户进行访谈，为Ralph的执行产出清晰的PRD。

If a topic is provided, use it. Otherwise ask for a short description of the feature or bug.

Initial prompt
- Ask what they want to build or fix and why.
Context scan
- Check for existing specs or documentation, such as
```
specs/README.md
```
  .
- Review project overview files like
```
README.md
```
  and package manifests.
Interview
- Ask only critical questions that affect scope and acceptance criteria.
- Cover: goals, users, constraints, scope, edge cases, success criteria.
Draft PRD
- Use the PRD template.
- Break into right sized user stories, each completable in one iteration.
- Order stories by dependency: schema, backend, UI, aggregation.
- Acceptance criteria must be verifiable.
Save output
- Save to
```
.prd/prd-<feature>.md
```
  .
- Create
```
.prd
```
  if missing.
Confirm and next steps
- Show the file path.
- Suggest converting with
```
/prd-to-json
```
  .

初始提示
- 询问用户想要构建或修复的内容及其原因。
上下文扫描
- 检查现有规范或文档，例如
```
specs/README.md
```
  。
- 查看项目概览文件，如
```
README.md
```
  和包清单。
访谈环节
- 仅询问影响范围和验收标准的关键问题。
- 涵盖：目标、用户群体、约束条件、范围、边缘情况、成功标准。
起草PRD
- 使用PRD模板。
- 拆分为合适规模的用户故事，每个故事可在一个迭代周期内完成。
- 按依赖关系排序故事：数据结构、后端、UI、聚合。
- 验收标准必须可验证。
保存输出
- 保存至
```
.prd/prd-<feature>.md
```
  。
- 若
```
.prd
```
  目录不存在则创建。
确认与后续步骤
- 展示文件路径。
- 建议使用
```
/prd-to-json
```
  进行格式转换。