Back to Details

prd-to-plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

PRD to Plan

PRD转实施计划

Break a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in 
./plans/
.
将PRD拆解为基于垂直切片（tracer bullets）的分阶段实施计划，输出为
./plans/
目录下的Markdown文件。

Process

流程

1. Confirm the PRD is in context

1. 确认PRD已在上下文内

The PRD should already be in the conversation. If it isn't, ask the user to paste it or point you to the file.
PRD应已存在于当前会话中。如果没有，请用户粘贴PRD内容或提供文件路径。

2. Explore the codebase

2. 调研代码库

If you have not already explored the codebase, do so to understand the current architecture, existing patterns, and integration layers.
如果你还未调研过代码库，先进行调研以了解当前架构、现有模式和集成层。

3. Identify durable architectural decisions

3. 确定长期有效的架构决策

Before slicing, identify high-level decisions that are unlikely to change throughout implementation:
  • Route structures / URL patterns
  • Database schema shape
  • Key data models
  • Authentication / authorization approach
  • Third-party service boundaries
These go in the plan header so every phase can reference them.
在切片前，先确定在整个实施过程中几乎不会变更的高层决策：
  • 路由结构 / URL模式
  • 数据库schema形态
  • 核心数据模型
  • 身份认证/授权方案
  • 第三方服务边界
这些内容会放在计划的头部，方便所有阶段参考。

4. Draft vertical slices

4. 起草垂直切片

Break the PRD into tracer bullet phases. Each phase is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
<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 - Do NOT include specific file names, function names, or implementation details that are likely to change as later phases are built - DO include durable decisions: route paths, schema shapes, data model names </vertical-slice-rules>
将PRD拆分为tracer bullet阶段。每个阶段都是一个贯穿所有集成层的端到端薄垂直切片，而非某一层的水平切片。
<vertical-slice-rules> - 每个切片提供一条覆盖所有层（schema、API、UI、测试）的窄但完整的路径 - 完成的切片可独立演示或验证 - 优先拆分为多个薄切片，而非少量厚切片 - 不要包含后续阶段开发时大概率会变更的具体文件名、函数名或实现细节 - 必须包含长期有效的决策：路由路径、schema形态、数据模型名称 </vertical-slice-rules>

5. Quiz the user

5. 与用户确认

Present the proposed breakdown as a numbered list. For each phase show:
  • Title: short descriptive name
  • User stories covered: which user stories from the PRD this addresses
Ask the user:
  • Does the granularity feel right? (too coarse / too fine)
  • Should any phases be merged or split further?
Iterate until the user approves the breakdown.
将拟好的拆解方案以编号列表形式呈现。每个阶段展示以下内容：
  • 标题：简短的描述性名称
  • 覆盖的用户故事：本阶段对应的PRD中的用户故事
向用户询问：
  • 粒度是否合适？（太粗 / 太细）
  • 是否有阶段需要合并或进一步拆分？
反复迭代直到用户认可拆解方案。

6. Write the plan file

6. 写入计划文件

Create 
./plans/
if it doesn't exist. Write the plan as a Markdown file named after the feature (e.g. 
./plans/user-onboarding.md
). Use the template below.
<plan-template>
如果
./plans/
目录不存在则创建该目录。按照功能命名计划文件（例如
./plans/user-onboarding.md
），将计划内容写入该Markdown文件，使用下方模板。
<plan-template>

Plan: <Feature Name>

计划：<功能名称>

Source PRD: <brief identifier or link>
来源PRD：<简短标识或链接>

Architectural decisions

架构决策

Durable decisions that apply across all phases:
  • Routes: ...
  • Schema: ...
  • Key models: ...
  • (add/remove sections as appropriate)
适用于所有阶段的长期有效决策：
  • 路由：...
  • Schema：...
  • 核心模型：...
  • （根据需要增减章节）

Phase 1: <Title>

阶段1：<标题>

User stories: <list from PRD>
用户故事：<来自PRD的列表>

What to build

构建内容

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
该垂直切片的简明描述。描述端到端行为，而非逐层的实现细节。

Acceptance criteria

验收标准

  • Criterion 1
  • Criterion 2
  • Criterion 3
  • 标准1
  • 标准2
  • 标准3

Phase 2: <Title>

阶段2：<标题>

User stories: <list from PRD>
用户故事：<来自PRD的列表>

What to build

构建内容

...
...

Acceptance criteria

验收标准

  • ...
<!-- Repeat for each phase --> </plan-template>
  • ...
<!-- 每个阶段重复以上结构 --> </plan-template>