dot-ai-prd-start

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

PRD Start - Begin Implementation Work

PRD启动 - 开始落地实施工作

Instructions

说明

You are helping initiate active implementation work on a specific Product Requirements Document (PRD). This command sets up the implementation context (validates readiness, creates branch, prepares environment) then hands off to

/prd-next

for task identification.

IMPORTANT: Do NOT include time estimates or effort estimates in your responses. Focus on setup and readiness without speculating on duration.

你将协助启动某一特定产品需求文档（PRD）的落地实施工作。该指令会搭建实施环境（验证就绪状态、创建分支、准备开发环境），然后将任务识别工作交接给

/prd-next

指令。

重要提示：回复中不得包含时间预估或工作量预估内容。请专注于环境搭建和就绪状态验证，不要推测耗时。

Process Overview

流程概述

Select Target PRD - Identify which PRD to implement
Validate PRD Readiness - Ensure the PRD is ready for implementation
Set Up Implementation Context - Create branch and prepare environment
Hand Off to prd-next - Delegate task identification to the appropriate prompt

选择目标PRD - 确定要实施的PRD
验证PRD就绪状态 - 确保PRD已准备好进入实施阶段
搭建实施环境 - 创建分支并准备开发环境
交接至prd-next - 将任务识别工作委托给对应的指令

Step 0: Check for PRD Argument

步骤0：检查PRD参数

If
prdNumber
argument is provided ({{prdNumber}}):

Skip context check and auto-detection
Use PRD #{{prdNumber}} directly
Proceed to Step 2 (PRD Readiness Validation)

If
prdNumber
argument is NOT provided:

Continue to context awareness check below

若提供了
prdNumber
参数（{{prdNumber}}）：

跳过上下文检查与自动识别
直接使用PRD #{{prdNumber}}
进入步骤2（PRD就绪状态验证）

若未提供
prdNumber
参数：

继续执行下方的上下文感知检查

Step 0b: Context Awareness Check

步骤0b：上下文感知检查

Check if PRD context is already clear from recent conversation:

Skip detection if recent conversation shows:

Recent PRD work discussed - "We just worked on PRD 29", "Just completed PRD update", etc.
Specific PRD mentioned - "PRD #X", "MCP Prompts PRD", etc.
PRD-specific commands used - Recent use of
```
/prd-update-progress
```
,
```
/prd-start
```
with specific PRD
Clear work context - Discussion of specific features, tasks, or requirements for a known PRD

If context is clear:

Skip to Step 2 (PRD Readiness Validation) using the known PRD

If context is unclear:

Continue to Step 1 (PRD Detection)

检查近期对话是否已明确PRD上下文：

若近期对话存在以下情况，跳过识别：

近期讨论过PRD工作 - 例如"我们刚完成PRD 29的工作"、"刚完成PRD更新"等表述
提及了特定PRD - 例如"PRD #X"、"MCP提示词PRD"等
使用过PRD专属指令 - 近期使用过
```
/prd-update-progress
```
、指定具体PRD的
```
/prd-start
```
等指令
工作上下文清晰 - 讨论了已知PRD的特定功能、任务或需求

若上下文清晰：

使用已知的PRD，直接进入步骤2（PRD就绪状态验证）

若上下文不清晰：

继续执行步骤1（PRD自动识别）

Step 1: Smart PRD Detection (Only if Context Unclear)

步骤1：智能PRD识别（仅当上下文不清晰时执行）

Auto-detect the target PRD using these context clues (in priority order):

Git Branch Analysis - Check current branch name for PRD patterns:
- ```
feature/prd-12-*
```
  → PRD 12
- ```
prd-13-*
```
  → PRD 13
- ```
feature/prd-*
```
  → Extract PRD number
Recent Git Commits - Look at recent commit messages for PRD references:
- "fix: PRD 12 documentation" → PRD 12
- "feat: implement prd-13 features" → PRD 13
Git Status Analysis - Check modified/staged files for PRD clues:
- Modified
```
prds/12-*.md
```
  → PRD 12
- Changes in feature-specific directories
Available PRDs Discovery - List all PRDs in
```
prds/
```
directory
Fallback to User Choice - Only if context detection fails, ask user to specify

Detection Logic:

High Confidence: Branch name matches PRD pattern (e.g.,
```
feature/prd-12-documentation-testing
```
)
Medium Confidence: Modified PRD files in git status or recent commits mention PRD
Low Confidence: Multiple PRDs available, use heuristics (most recent, largest)
No Context: Present available options to user

If context detection fails, ask the user:

markdown

undefined

使用以下上下文线索自动识别目标PRD（按优先级排序）：

Git分支分析 - 检查当前分支名称是否符合PRD命名模式：
- ```
feature/prd-12-*
```
  → 对应PRD 12
- ```
prd-13-*
```
  → 对应PRD 13
- ```
feature/prd-*
```
  → 提取PRD编号
近期Git提交记录 - 查看近期提交信息中是否有PRD相关引用：
- "fix: PRD 12 documentation" → 对应PRD 12
- "feat: implement prd-13 features" → 对应PRD 13
Git状态分析 - 检查已修改/暂存的文件中是否有PRD线索：
- 修改了
```
prds/12-*.md
```
  → 对应PRD 12
- 功能专属目录中有变更
可用PRD发现 - 列出
```
prds/
```
目录下的所有PRD
回退至用户选择 - 仅当上下文识别失败时，请求用户指定

识别逻辑：

高置信度：分支名称匹配PRD模式（例如
```
feature/prd-12-documentation-testing
```
）
中置信度：Git状态中存在已修改的PRD文件，或近期提交记录提及PRD
低置信度：存在多个可用PRD，使用启发式规则（最新的、规模最大的）
无上下文：向用户展示可用选项

若上下文识别失败，向用户询问：

markdown

undefined

Which PRD would you like to start implementing?

你想要开始实施哪份PRD？

Please provide the PRD number (e.g., "12", "PRD 12", or "36").

Not sure which PRD to work on? Execute

dot-ai:prds-get

prompt to see all available PRDs organized by priority and readiness.

Your choice: [Wait for user input]


**Once PRD is identified:**
- Read the PRD file from `prds/[issue-id]-[feature-name].md`

请提供PRD编号（例如："12"、"PRD 12"或"36"）。

不确定要选择哪份PRD？ 执行

dot-ai:prds-get

指令查看所有按优先级和就绪状态排序的可用PRD。

你的选择：[等待用户输入]


**一旦确定PRD：**
- 从`prds/[issue-id]-[feature-name].md`读取PRD文件

Step 2: PRD Readiness Validation

步骤2：PRD就绪状态验证

Before starting implementation, validate that the PRD is ready:

开始实施前，验证PRD是否已准备就绪：

Requirements Validation

需求验证

Functional Requirements: Are core requirements clearly defined and complete?
Success Criteria: Are measurable success criteria established?
Dependencies: Are all external dependencies identified and available?
Risk Assessment: Have major risks been identified and mitigation plans created?

功能需求：核心需求是否已清晰定义且完整？
成功标准：是否已建立可衡量的成功标准？
依赖项：是否已识别所有外部依赖项且可用？
风险评估：是否已识别主要风险并制定缓解方案？

Documentation Analysis

文档分析

For documentation-first PRDs:

Specification completeness: Is the feature fully documented with user workflows?
Integration points: Are connections with existing features documented?
API/Interface definitions: Are all interfaces and data structures specified?
Examples and usage: Are concrete usage examples provided?

对于文档优先的PRD：

规范完整性：功能是否已通过用户流程完整记录？
集成点：与现有功能的连接是否已记录？
API/接口定义：所有接口和数据结构是否已明确？
示例与用法：是否提供了具体的使用示例？

Implementation Readiness Checklist

实施就绪检查清单

markdown

undefined

markdown

undefined

PRD Readiness Check

PRD就绪检查

All functional requirements defined
Success criteria measurable
Dependencies available
Documentation complete
Integration points clear
Implementation approach decided


**If PRD is not ready:** Inform the user what's missing and suggest they complete PRD planning first.

所有功能需求已定义
成功标准可衡量
依赖项可用
文档完整
集成点清晰
实施方案已确定


**若PRD未就绪：** 告知用户缺失内容，并建议先完成PRD规划工作。

Step 3: Implementation Context Setup

步骤3：实施环境搭建

⚠️ MANDATORY: Complete this step BEFORE proceeding to Step 4

⚠️ 强制要求：完成此步骤后再进入步骤4

Git Branch Management

Git分支管理

Check current branch: Run
```
git branch --show-current
```

If on
main
or
master
: Create and switch to feature branch:

bash

git checkout -b feature/prd-[issue-id]-[feature-name]

If already on a feature branch: Verify it's the correct branch for this PRD

检查当前分支：执行
```
git branch --show-current
```

若当前在
main
或
master
分支：创建并切换到功能分支：

bash

git checkout -b feature/prd-[issue-id]-[feature-name]

若已在功能分支：验证该分支是否为当前PRD的对应分支

Development Environment Setup

开发环境准备

Dependencies: Install any new dependencies required by the PRD
Configuration: Set up any configuration needed for development
Test data: Prepare test data or mock services

依赖项：安装PRD所需的所有新依赖项
配置：设置开发所需的各项配置
测试数据：准备测试数据或模拟服务

Step 3 Checkpoint (REQUIRED)

步骤3检查点（必填）

You MUST display this confirmation before proceeding to Step 4:

markdown

undefined

进入步骤4前，必须显示以下确认信息：

markdown

undefined

Environment Setup ✅

环境搭建完成 ✅

Branch:
```
[current-branch-name]
```
✅
Status: [Created new branch / Already on correct branch / Staying on main (reason)]


**DO NOT proceed to Step 4 until branch setup is confirmed.**

分支：
```
[current-branch-name]
```
✅
状态：[已创建新分支 / 已在正确分支上 / 保留在main分支（原因）]


**在分支搭建确认完成前，不得进入步骤4。**

Step 4: Hand Off to prd-next

步骤4：交接至prd-next

Once the implementation context is set up, present this message to the user:

markdown

undefined

环境搭建完成后，向用户展示以下信息：

markdown

undefined

Ready for Implementation 🚀

准备就绪，可开始实施 🚀

PRD: [PRD Name] (#[PRD Number]) Branch:

[branch-name]

Status: Ready for development

To identify and start working on your first task, run

/prd-next


**⚠️ STOP HERE - DO NOT:**
- Identify or recommend tasks to work on
- Analyze implementation priorities or critical paths
- Start any implementation work
- Continue beyond presenting the handoff message

`/prd-next` handles all task identification and implementation guidance.

PRD：[PRD名称]（#[PRD编号]）分支：

[branch-name]

状态：已准备好进入开发阶段

要识别并开始处理首个任务，请执行

/prd-next

指令。


**⚠️ 到此为止 - 禁止：**
- 识别或推荐待处理任务
- 分析实施优先级或关键路径
- 启动任何实施工作
- 在展示交接信息后继续后续内容

所有的任务识别、实施指导工作均由`/prd-next`负责。

Success Criteria

成功标准

This command should:

✅ Successfully identify the target PRD for implementation
✅ Validate that the PRD is ready for development work
✅ Set up proper implementation context (branch, environment)
✅ Hand off to
```
/prd-next
```
for task identification
✅ Bridge the gap between PRD planning and development setup

该指令应实现：

✅ 成功识别目标实施PRD
✅ 验证PRD已准备好进入开发阶段
✅ 搭建合适的实施环境（分支、开发环境）
✅ 将任务识别工作交接给
```
/prd-next
```
✅ 填补PRD规划与开发搭建之间的空白

Notes

注意事项

This command focuses on setup only - it validates readiness, creates the branch, and prepares the environment
Once setup is complete,
```
/prd-next
```
handles all task identification, implementation guidance, and progress tracking

该指令仅专注于环境搭建 - 验证就绪状态、创建分支、准备开发环境
环境搭建完成后，所有的任务识别、实施指导与进度跟踪工作均由
```
/prd-next
```
负责