Back to Details

to-prd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
该Skill会结合当前对话上下文及对代码库的理解生成一份PRD。请勿向用户提问——只需整合你已掌握的信息即可。

Process

流程

  1. Explore the repo to understand the current state of the codebase, if you haven't already.
  2. Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.
A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
  1. Write the PRD using the template below and submit it as a GitHub issue.
<prd-template>
  1. 如果你还未了解代码库当前状态，请先浏览代码仓库。
  2. 概述完成实现所需构建或修改的主要模块。主动寻找可提取的深度模块，这些模块可独立进行测试。
深度模块（与浅模块相对）指的是通过简单、可测试且极少变更的接口封装大量功能的模块。
与用户确认这些模块是否符合他们的预期。询问用户希望为哪些模块编写测试。
  1. 使用下方模板编写PRD并提交为GitHub Issue。
<prd-template>

Problem Statement

问题陈述

The problem that the user is facing, from the user's perspective.
从用户视角描述用户面临的问题。

Solution

解决方案

The solution to the problem, from the user's perspective.
从用户视角描述问题的解决方案。

User Stories

用户故事

A LONG, numbered list of user stories. Each user story should be in the format of:
  1. As an <actor>, I want a <feature>, so that <benefit>
<user-story-example> 1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending </user-story-example>
This list of user stories should be extremely extensive and cover all aspects of the feature.
一份详尽的编号列表，每个用户故事需遵循以下格式：
  1. 作为<角色>，我想要<功能>，以便<收益>
<user-story-example> 1. 作为移动银行客户，我想要查看账户余额，以便能更明智地做出消费决策 </user-story-example>
这份用户故事列表需极为详尽，覆盖该功能的所有方面。

Implementation Decisions

实现决策

A list of implementation decisions that were made. This can include:
  • The modules that will be built/modified
  • The interfaces of those modules that will be modified
  • Technical clarifications from the developer
  • Architectural decisions
  • Schema changes
  • API contracts
  • Specific interactions
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
已确定的实现决策列表，可包含：
  • 需构建/修改的模块
  • 需修改的模块接口
  • 来自开发者的技术说明
  • 架构决策
  • 架构变更
  • API契约
  • 特定交互逻辑
请勿包含具体文件路径或代码片段，这些内容可能会很快过时。

Testing Decisions

测试决策

A list of testing decisions that were made. Include:
  • A description of what makes a good test (only test external behavior, not implementation details)
  • Which modules will be tested
  • Prior art for the tests (i.e. similar types of tests in the codebase)
已确定的测试决策列表，需包含：
  • 优质测试的定义（仅测试外部行为，而非实现细节）
  • 需测试的模块
  • 测试参考案例（即代码库中类似类型的测试）

Out of Scope

范围外内容

A description of the things that are out of scope for this PRD.
描述本PRD不涵盖的内容。

Further Notes

补充说明

Any further notes about the feature.
</prd-template>
关于该功能的其他补充说明。
</prd-template>