plan-validate

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

CRITICAL: Do NOT use
EnterPlanMode
tool — it blocks Write/Edit/Task tools. Follow the workflow below.

重要提示： 请勿使用
EnterPlanMode
工具——它会阻止Write/Edit/Task工具的使用。请遵循以下工作流程。

Summary

摘要

Goal: Validate an implementation plan by interviewing the user with critical questions to confirm assumptions and surface risks before coding.

Step	Action	Key Notes
1	Read plan files	`plan.md` and all `phase-*.md` -- find decision points, assumptions, risks
2	Extract question topics	Scan for architecture, assumptions, tradeoffs, risks, scope keywords
3	Generate questions	2-4 concrete options per question, mark recommended option
4	Interview user	Use AskUserQuestion with configured question count (min-max)
5	Document answers	Add `## Validation Summary` to plan.md with confirmed decisions

Key Principles:

Only ask about genuine decision points -- don't manufacture artificial choices
Prioritize questions that could change implementation significantly
Document answers but do NOT modify phase files -- just note what needs updating

目标： 在编码前，通过向用户提出关键问题进行访谈，验证实施计划，确认假设并发现潜在风险。

步骤	操作	关键说明
1	阅读方案文件	读取 `plan.md` 和所有 `phase-*.md` 文件——找出决策点、假设和风险
2	提取问题主题	扫描架构、假设、权衡、风险、范围相关关键词
3	生成问题	每个问题提供2-4个具体选项，并标记推荐选项
4	用户访谈	使用AskUserQuestion工具，按照配置的问题数量范围（最小-最大）进行提问
5	记录答案	在plan.md中添加 `## Validation Summary` 部分，记录已确认的决策

核心原则：

仅针对真实存在的决策点提问——不要编造无意义的选项
优先提问那些可能会显著改变实施方式的问题
记录答案，但不要修改阶段文件——只需记录需要更新的内容

Your mission

你的任务

Interview the user with critical questions to validate assumptions, confirm decisions, and surface potential issues in an implementation plan before coding begins.

在编码开始前，通过向用户提出关键问题进行访谈，验证实施计划中的假设、确认决策，并发现潜在问题。

Plan Resolution

方案定位

If
```
$ARGUMENTS
```
provided → Use that path
Else check
```
## Plan Context
```
section → Use active plan path
If no plan found → Ask user to specify path or run
```
/plan-hard
```
first

若提供了
```
$ARGUMENTS
```
参数 → 使用该路径
否则检查
```
## Plan Context
```
部分 → 使用当前激活的方案路径
若未找到方案 → 请用户指定路径，或先运行
```
/plan-hard
```
命令

Configuration (from injected context)

配置信息（来自注入的上下文）

Check

## Plan Context

section for validation settings:

```
mode
```
- Controls auto/prompt/off behavior
```
questions
```
- Range like
```
3-8
```
(min-max)

These values are automatically injected from user config. Use them as constraints.

查看

## Plan Context

部分获取验证设置：

```
mode
```
- 控制自动/提示/关闭行为
```
questions
```
- 数量范围，如
```
3-8
```
（最小-最大）

这些值会从用户配置中自动注入，请将其作为约束条件使用。

Workflow

工作流程

Step 1: Read Plan Files

步骤1：读取方案文件

Read the plan directory:

```
plan.md
```
- Overview and phases list
```
phase-*.md
```
- All phase files
Look for decision points, assumptions, risks, tradeoffs

读取方案目录中的文件：

```
plan.md
```
- 方案概述和阶段列表
```
phase-*.md
```
- 所有阶段文件
查找决策点、假设、风险和权衡点

Step 2: Extract Question Topics

步骤2：提取问题主题

Scan plan content for:

Category	Keywords to detect
Architecture	"approach", "pattern", "design", "structure", "database", "API"
Assumptions	"assume", "expect", "should", "will", "must", "default"
Tradeoffs	"tradeoff", "vs", "alternative", "option", "choice", "either/or"
Risks	"risk", "might", "could fail", "dependency", "blocker", "concern"
Scope	"phase", "MVP", "future", "out of scope", "nice to have"
Reasoning	Check: Does Architecture section explain WHY, not just WHAT? Does Risk Assessment include failure modes? Is there a Design Intent or Trade-offs section?

扫描方案内容，寻找以下类别：

类别	需检测的关键词
架构	"approach", "pattern", "design", "structure", "database", "API"
假设	"assume", "expect", "should", "will", "must", "default"
权衡	"tradeoff", "vs", "alternative", "option", "choice", "either/or"
风险	"risk", "might", "could fail", "dependency", "blocker", "concern"
范围	"phase", "MVP", "future", "out of scope", "nice to have"
合理性	检查：架构部分是否解释了原因，而非仅说明内容？风险评估是否包含故障模式？是否有设计意图或权衡分析部分？

Step 3: Generate Questions

步骤3：生成问题

For each detected topic, formulate a concrete question:

Question format rules:

Each question must have 2-4 concrete options
Mark recommended option with "(Recommended)" suffix
Include "Other" option is automatic - don't add it
Questions should surface implicit decisions

Example questions:

Category: Architecture
Question: "How should the validation results be persisted?"
Options:
1. Save to plan.md frontmatter (Recommended) - Updates existing plan
2. Create validation-answers.md - Separate file for answers
3. Don't persist - Ephemeral validation only

Category: Assumptions
Question: "The plan assumes API rate limiting is not needed. Is this correct?"
Options:
1. Yes, rate limiting not needed for MVP
2. No, add basic rate limiting now (Recommended)
3. Defer to Phase 2

针对每个检测到的主题，构建具体问题：

问题格式规则：

每个问题必须包含2-4个具体选项
用"(Recommended)"后缀标记推荐选项
自动包含"Other"选项——无需手动添加
问题应能揭示隐含的决策

示例问题：

Category: Architecture
Question: "How should the validation results be persisted?"
Options:
1. Save to plan.md frontmatter (Recommended) - Updates existing plan
2. Create validation-answers.md - Separate file for answers
3. Don't persist - Ephemeral validation only

Category: Assumptions
Question: "The plan assumes API rate limiting is not needed. Is this correct?"
Options:
1. Yes, rate limiting not needed for MVP
2. No, add basic rate limiting now (Recommended)
3. Defer to Phase 2

Step 4: Interview User

步骤4：用户访谈

Use

AskUserQuestion

tool to present questions.

Rules:

Use question count from

## Plan Context

→

Validation: mode=X, questions=MIN-MAX

Group related questions when possible (max 4 questions per tool call)
Focus on: assumptions, risks, tradeoffs, architecture

使用

AskUserQuestion

工具呈现问题。

规则：

使用

## Plan Context

中指定的问题数量 →

Validation: mode=X, questions=MIN-MAX

尽可能将相关问题分组（每次工具调用最多4个问题）
重点关注：假设、风险、权衡、架构

Step 5: Document Answers

步骤5：记录答案

After collecting answers, update the plan:

Add
```
## Validation Summary
```
section to
```
plan.md
```
:

markdown

undefined

收集答案后，更新方案：

在
```
plan.md
```
中添加
```
## Validation Summary
```
部分：

markdown

undefined

Validation Summary

Validated: {date} Questions asked: {count}

Confirmed Decisions

{decision 1}: {user choice}
{decision 2}: {user choice} 1

{decision 1}: {user choice}
{decision 2}: {user choice} 1

Action Items

{any changes needed based on answers}


1. If answers require plan changes, note them but **do not modify phase files** - just document what needs updating.

{any changes needed based on answers}


2. 如果答案要求修改方案，只需记录需要更新的内容，**不要修改阶段文件**。

Output

输出要求

After validation completes, provide summary:

Number of questions asked
Key decisions confirmed
Any items flagged for plan revision
Recommendation: proceed to implementation or revise plan first

验证完成后，提供以下总结：

提出的问题数量
已确认的关键决策
任何需要修订方案的标记项
建议：直接进入实施阶段，还是先修订方案

Important Notes

重要提示

IMPORTANT: Only ask questions about genuine decision points - don't manufacture artificial choices. IMPORTANT: If plan is simple with few decisions, it's okay to ask fewer than min questions. IMPORTANT: Prioritize questions that could change implementation significantly.

重点： 仅针对真实存在的决策点提问——不要编造无意义的选项 重点： 如果方案简单，决策点很少，提问数量可以少于最小要求 重点： 优先提问那些可能会显著改变实施方式的问题

IMPORTANT Task Planning Notes

重要的任务规划提示

Always plan and break many small todo tasks
Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

始终要规划并拆分多个小型待办任务
始终要添加一个最终审核待办任务，在结束时检查已完成的工作，找出需要修复或优化的内容