prd-to-issues

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

PRD to Issues

PRD 转 Issue

Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets).

使用垂直切片（追踪式）将PRD拆分为可独立承接的GitHub Issue。

Process

流程

1. Locate the PRD

1. 定位PRD

Ask the user for the PRD GitHub issue number (or URL).

If the PRD is not already in your context window, fetch it with

gh issue view <number>

(with comments).

向用户索要PRD的GitHub Issue编号（或URL）。

如果PRD尚未在你的上下文窗口中，使用

gh issue view <number>

（包含评论）获取它。

2. Explore the codebase (optional)

2. 探索代码库（可选）

If you have not already explored the codebase, do so to understand the current state of the code.

如果你还未探索过代码库，请进行探索以了解代码的当前状态。

3. Draft vertical slices

3. 草拟垂直切片

Break the PRD into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.

<vertical-slice-rules> - Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones </vertical-slice-rules>

将PRD拆分为追踪式Issue。每个Issue是一个贯穿所有集成层的精简垂直切片，而非单一层面的水平切片。

切片可以是“HITL”或“AFK”类型。HITL切片需要人工介入，例如架构决策或设计评审。AFK切片无需人工介入即可实现并合并。在可能的情况下，优先选择AFK类型。

<vertical-slice-rules> - 每个切片提供一条贯穿所有层级（schema、API、UI、测试）的狭窄但完整的路径 - 完成后的切片可独立进行演示或验证 - 优先选择多个精简切片，而非少量厚重切片 </vertical-slice-rules>

4. Quiz the user

4. 与用户确认

Present the proposed breakdown as a numbered list. For each slice, show:

Title: short descriptive name
Type: HITL / AFK
Blocked by: which other slices (if any) must complete first
User stories covered: which user stories from the PRD this addresses

Ask the user:

Does the granularity feel right? (too coarse / too fine)
Are the dependency relationships correct?
Should any slices be merged or split further?
Are the correct slices marked as HITL and AFK?

Iterate until the user approves the breakdown.

将拟议的拆分方案以编号列表形式呈现。对于每个切片，需展示：

标题：简短描述性名称
类型：HITL / AFK
依赖项：哪些其他切片（如有）必须先完成
覆盖的用户故事：该切片解决PRD中的哪些用户故事

向用户询问：

粒度是否合适？（太粗/太细）
依赖关系是否正确？
是否需要合并或进一步拆分某些切片？
HITL和AFK的标记是否正确？

反复迭代直到用户批准该拆分方案。

5. Create the GitHub issues

5. 创建GitHub Issue

For each approved slice, create a GitHub issue using

gh issue create

. Use the issue body template below.

Create issues in dependency order (blockers first) so you can reference real issue numbers in the "Blocked by" field.

<issue-template>

对于每个获批的切片，使用

gh issue create

创建GitHub Issue。使用以下Issue正文模板。

按照依赖顺序创建Issue（先创建被依赖的Issue），以便在“依赖项”字段中引用真实的Issue编号。

<issue-template>

Parent PRD

父PRD

#<prd-issue-number>

What to build

需构建内容

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. Reference specific sections of the parent PRD rather than duplicating content.

该垂直切片的简要描述。描述端到端的行为，而非逐层的实现细节。引用父PRD的特定章节，而非重复内容。

Acceptance criteria

验收标准

Blocked by

依赖项

Blocked by #<issue-number> (if any)

Or "None - can start immediately" if no blockers.

依赖于 #<issue-number>（如有）

若无依赖项则填写“无 - 可立即开始”。

User stories addressed

覆盖的用户故事

Reference by number from the parent PRD:

User story 3
User story 7

</issue-template>

Do NOT close or modify the parent PRD issue.

引用父PRD中的编号：

用户故事3
用户故事7

</issue-template>

请勿关闭或修改父PRD Issue。