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.
The issue tracker should be accessible via 
gh
. If label vocabulary is needed, check the project's AGENTS.md or issue templates.
该Skill会利用当前对话上下文和对代码库的理解生成PRD。请勿询问用户——仅基于已掌握的信息进行整合。
问题追踪器应可通过
gh
访问。若需要标签词汇，请查看项目的AGENTS.md或问题模板。

Process

流程

  1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
  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, then publish it to the project issue tracker. Apply the 
    needs-triage
    triage label so it enters the normal triage flow.
<prd-template>
  1. 若尚未了解代码库当前状态，请探索仓库进行了解。在整个PRD中使用项目的领域术语表词汇，并遵守你所涉及领域的任何ADRs。
  2. 概述完成实现所需构建或修改的主要模块。积极寻找可提取为独立测试的深度模块的机会。
深度模块（相对于浅模块）是指在简单、可测试且很少变更的接口中封装大量功能的模块。
与用户确认这些模块是否符合他们的预期。询问用户希望为哪些模块编写测试。
  1. 使用下方模板编写PRD，然后发布到项目问题追踪器。添加
    needs-triage
    分类标签，使其进入常规分类流程。
<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>