Back to Details

to-prd

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
这个 skill 使用当前 conversation context 和 codebase understanding 产出 PRD。不要访谈用户，只综合你已经知道的内容。
Issue tracker 和 triage label vocabulary 应该已经提供给你；如果没有，运行 
/setup-matt-pocock-skills
。
This skill generates a PRD using the current conversation context and codebase understanding. Do not interview the user; only synthesize what you already know.
The issue tracker and triage label vocabulary should have been provided to you; if not, run 
/setup-matt-pocock-skills
.

Process

Process

  1. 如果还没有探索 repo，先探索它以理解 codebase 当前状态。在 PRD 中始终使用项目 domain glossary vocabulary，并遵守相关 ADRs。
  2. 草拟完成 implementation 需要 build 或 modify 的主要 modules。主动寻找可以抽出 deep modules 并独立测试的机会。
Deep module（相对 shallow module）会把大量功能封装在一个简单、可测试、很少变化的 interface 后面。
与用户确认这些 modules 是否符合预期。与用户确认他们希望为哪些 modules 写 tests。
  1. 使用下面模板写 PRD，并发布到项目 issue tracker。应用 
    ready-for-agent
    triage label；不需要额外 triage。
<prd-template>
  1. If you haven't explored the repo yet, explore it first to understand the current state of the codebase. Always use the project's domain glossary vocabulary in the PRD and comply with relevant ADRs.
  2. Draft the main modules that need to be built or modified to complete the implementation. Proactively look for opportunities to extract deep modules and test them independently.
A Deep module (as opposed to a shallow module) encapsulates a large amount of functionality behind a simple, testable, and rarely changing interface.
Confirm with the user whether these modules meet expectations. Confirm with the user which modules they want tests written for.
  1. Write the PRD using the template below and publish it to the project issue tracker. Apply the 
    ready-for-agent
    triage label; no additional triage is needed.
<prd-template>

Problem Statement

Problem Statement

用户正在面对的问题，从用户视角描述。
Describe the problem the user is facing from the user's perspective.

Solution

Solution

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

User Stories

User Stories

一份很长的编号 user stories 列表。每条 user story 使用以下格式：
  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>
这份 user stories 列表应该非常完整，覆盖 feature 的所有方面。
A long numbered list of user stories. Each user story uses the following format:
  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 very comprehensive, covering all aspects of the feature.

Implementation Decisions

Implementation Decisions

已作出的 implementation decisions 列表。可以包括：
  • 将 build/modify 的 modules
  • 将 modify 的 module interfaces
  • 来自 developer 的技术澄清
  • Architectural decisions
  • Schema changes
  • API contracts
  • Specific interactions
不要包含具体 file paths 或 code snippets。它们可能很快过时。
例外：如果 prototype 产出的 snippet 比 prose 更精确地编码了某个决策（state machine、reducer、schema、type shape），可以内联到相关 decision 中，并简短说明它来自 prototype。只保留决策密集部分，不要放完整 working demo。
A list of made implementation decisions. It can include:
  • Modules to be built/modified
  • Module interfaces to be modified
  • Technical clarifications from developers
  • Architectural decisions
  • Schema changes
  • API contracts
  • Specific interactions
Do not include specific file paths or code snippets. They may become outdated quickly.
Exception: If a snippet generated by a prototype encodes a decision more precisely than prose (state machine, reducer, schema, type shape), it can be inline into the relevant decision with a brief note stating it comes from the prototype. Only keep the decision-dense parts; do not include a complete working demo.

Testing Decisions

Testing Decisions

已作出的 testing decisions 列表。包括：
  • 什么是好测试的描述（只测试 external behavior，不测试 implementation details）
  • 哪些 modules 会被测试
  • 测试的 prior art（即 codebase 中类似类型的 tests）
A list of made testing decisions. It includes:
  • Description of what constitutes a good test (only test external behavior, not implementation details)
  • Which modules will be tested
  • Prior art for testing (i.e., similar types of tests in the codebase)

Out of Scope

Out of Scope

本 PRD 范围外事项的描述。
Description of items outside the scope of this PRD.

Further Notes

Further Notes

关于 feature 的其他 notes。
</prd-template>
Additional notes about the feature.
</prd-template>