Back to Details

structured-plan-mode

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Structured Plan Mode Skill

结构化规划模式技能

Purpose

用途

This skill provides a structured approach for planning and tracking complex feature implementations through systematic task decomposition. It helps break down large, multi-component features into manageable tasks with clear goals, dependencies, and success criteria.
此技能为规划和跟踪复杂功能实现提供了结构化方法，通过系统性任务分解，将大型、多组件功能拆解为具备清晰目标、依赖关系和成功标准的可管理任务。

When to Use This Skill

适用场景

Use this skill when:
  • Complex features: Features requiring multiple components or integration points
  • Multi-step implementations: Work spanning several days with interdependent tasks
  • Pattern-setting work: Features that will establish patterns for future development
  • Research required: Work where multiple approaches need evaluation
Do NOT use this skill for:
  • Simple bug fixes
  • Trivial feature additions
  • One-off scripts or experiments
  • Work with single, clear implementation path
适用于以下场景：
  • 复杂功能：需要多个组件或集成点的功能
  • 多步骤实现：耗时数天、任务相互依赖的工作
  • 模式设定工作：将为未来开发确立模式的功能
  • 需要调研的工作：需要评估多种实现方案的工作
不适用于以下场景：
  • 简单bug修复
  • 微小功能新增
  • 一次性脚本或实验
  • 只有单一、明确实现路径的工作

How to Use the Skill

如何使用此技能

IMPORTANT: This is a PHASED approach. Complete each phase BEFORE moving to the next.
重要提示：这是一个分阶段的方法，必须完成当前阶段后才能进入下一阶段。

Phase 1: Initial Setup

阶段1：初始设置

Actions:
  1. Create 
    .plans/[feature-name]/
    directory (in current project directory)
  2. Copy 
    assets/plan-template.md
    to 
    .plans/[feature-name]/plan.md
  3. Create 
    .plans/[feature-name]/tasks/
    directory for task files
  4. Replace 
    [Feature Name]
    with your feature name in plan.md
  5. Fill in basic overview and context
  6. Create Research section with:
    • Goal
    • Context
    • Strategy Proposals (leave empty for now)
    • Leave "Selected Approach" EMPTY
  7. Create a todo list by using TodoWrite based on the phases below
TodoWrite tracks ONLY phases 1-4:
- [ ] Phase 1: Setup template with Research section
- [ ] Phase 2: Conduct research and iterate with user
- [ ] Phase 3: Finalize selected approach
- [ ] Phase 4: Create implementation tasks (T01-T0N)
Mark Phase 1 as completed in TodoWrite
Output: Skeleton plan document with Research section defined and todo list created for phases 1-4
操作步骤：
  1. 在当前项目目录下创建 
    .plans/[feature-name]/
    目录
  2. 将 
    assets/plan-template.md
    复制到 
    .plans/[feature-name]/plan.md
  3. 创建 
    .plans/[feature-name]/tasks/
    目录用于存放任务文件
  4. 将 plan.md 中的 
    [Feature Name]
    替换为你的功能名称
  5. 填写基本概述和背景信息
  6. 创建调研部分，包含：
    • 目标
    • 背景
    • 策略方案（暂时留空）
    • 请将“选定方案”部分留空
  7. 使用 TodoWrite 根据以下阶段创建待办事项列表
TodoWrite 仅跟踪阶段1-4：
- [ ] Phase 1: Setup template with Research section
- [ ] Phase 2: Conduct research and iterate with user
- [ ] Phase 3: Finalize selected approach
- [ ] Phase 4: Create implementation tasks (T01-T0N)
在 TodoWrite 中标记阶段1为已完成
输出结果：包含已定义调研部分的规划文档框架，以及阶段1-4的待办事项列表

Phase 2: Conduct Research and Iterate with User

阶段2：开展调研并与用户迭代沟通

Research Process (Iterative):
  1. Explore codebase: Read relevant files, find similar patterns
  2. Document findings incrementally: Add to "Key Findings" as you discover
  3. Identify 2-3 approach options: Add to "Strategy Proposals" section
  4. ITERATE with user on EACH proposal:
    • Present each proposal with trade-offs (pros/cons)
    • Use 
      AskUserQuestion
      to clarify requirements and constraints
    • User may correct assumptions - update research based on feedback
    • Refine understanding through questions (typically 3-5 questions, but quality over quantity)
    • If user strongly prefers one approach early, you may skip detailed discussion of remaining options
  5. Proactively ask if research is complete: Once you've explored all options and answered clarifying questions, explicitly ask: "Are you ready to select an approach?"
CRITICAL:
  • This is an ITERATIVE process - expect back-and-forth discussion on each proposal
  • Use AskUserQuestion frequently to refine understanding
  • Don't wait for user to say research is done - ASK them proactively
Mark Phase 2 as completed in TodoWrite when user confirms that research is complete
Output: Research with 2-3 Strategy Proposals documented and reviewed with user
调研流程（迭代式）：
  1. 探索代码库：阅读相关文件，查找类似模式
  2. 逐步记录调研结果：将发现的内容添加到“关键发现”部分
  3. 确定2-3种方案选项：添加到“策略方案”部分
  4. 针对每个方案与用户迭代沟通：
    • 呈现每个方案及其优缺点（权衡）
    • 使用 
      AskUserQuestion
      明确需求和约束条件
    • 用户可能会纠正你的假设 - 根据反馈更新调研内容
    • 通过提问细化理解（通常3-5个问题，重质不重量）
    • 如果用户很早就明确偏好某一方案，你可以跳过对剩余方案的详细讨论
  5. 主动询问调研是否完成：当你探索完所有选项并解答了澄清问题后，明确询问：“你是否已准备好选定方案？”
关键注意事项:
  • 这是一个迭代过程 - 预计会针对每个方案进行多次来回讨论
  • 频繁使用 AskUserQuestion 来细化理解
  • 不要等用户说调研完成 - 主动询问他们
当用户确认调研完成后，在 TodoWrite 中标记阶段2为已完成
输出结果：包含2-3种已记录并与用户评审过的策略方案的调研文档

Phase 3: Finalize Selected Approach

阶段3：确定最终选定方案

Actions:
  1. Ask the user to select an approach using AskUserQuestion (present the 2-3 researched approaches as formal selection options)
  2. Once user confirms their selection, fill "Selected Approach" section with:
    • Decision: Which approach was selected (must match user's confirmed preference)
    • Rationale: Why this approach was chosen over alternatives
    • Key Findings: Summarize important discoveries from research
    • Implementation Plan: High-level steps (5-7 bullet points)
  3. Mark all research action items as [x] completed
  4. Change research status to ✅ Completed
  5. Update Progress Summary to show research complete
Mark Phase 3 as completed in TodoWrite once Selected Approach section is fully documented
Output: Research fully documented with clear decision and rationale
操作步骤：
  1. 使用 AskUserQuestion 请用户选定方案（将调研得出的2-3种方案作为正式选项呈现）
  2. 一旦用户确认选定方案，在“选定方案”部分填写：
    • 决策：选定的方案（必须与用户确认的偏好一致）
    • 理由：为何选择此方案而非其他方案
    • 关键发现：总结调研中的重要发现
    • 实施计划：高级步骤（5-7个要点）
  3. 将所有调研行动项标记为 [x] 已完成
  4. 将调研状态改为 ✅ 已完成
  5. 更新进度摘要以显示调研已完成
当“选定方案”部分填写完成后，在 TodoWrite 中标记阶段3为已完成
输出结果：包含明确决策和理由的完整调研文档

Phase 4: Create Implementation Tasks (ONLY AFTER Phase 1-3 Complete)

阶段4：创建实现任务（仅在完成阶段1-3后进行）

IMPORTANT: Before creating tasks, read 
references/task-planning-guide.md
to understand:
  • How to break down work into appropriate task sizes
  • Task file structure and required sections
  • Best practices for defining clear requirements and action items
  • How to set proper dependencies between tasks
Actions: NOW create T01, T02, T03, ...T0N as separate files in 
.plans/[feature-name]/tasks/
based on selected approach
  • Number of tasks depends on complexity (simple: 1-2, medium: 3-5, complex: 5+)
  • Break down into manageable chunks (2-5 days each)
Step-by-Step: Creating a Task File
For each task you need to create:
  1. Copy the template:
    bash
    cp [path-to-task-template.md] .plans/[feature-name]/tasks/T01.md
  2. Update task header: Replace 
    T0X
    with actual task number (T01, T02, etc.)
  3. Fill in core sections:
    • Goal: One clear, measurable objective
    • Context: How it relates to the feature and selected approach
    • Requirements: Detailed specifications with implementation steps
    • Action Items: Specific checkboxes for work to complete
  4. Update metadata: Set Status (🟡 Planned), Effort (Small/Medium/Large), Blocked By
  5. Add to Progress Summary: Update plan.md with link: 
    - [ ] [**T01**: Task Name](tasks/T01.md) - Status: 🟡 Planned
Mark Phase 4 as completed in TodoWrite
Output: Complete task breakdown (T01.md - T0N.md files) in tasks/ folder, all linked from plan.md Progress Summary
重要提示：在创建任务前，请阅读 
references/task-planning-guide.md
以了解：
  • 如何将工作拆解为合适大小的任务
  • 任务文件结构和必填部分
  • 定义清晰需求和行动项的最佳实践
  • 如何设置任务间的合理依赖关系
操作步骤： 现在根据选定方案在 
.plans/[feature-name]/tasks/
目录下创建独立的 T01、T02、T03...T0N 文件
  • 任务数量取决于复杂度（简单：1-2个，中等：3-5个，复杂：5个以上）
  • 拆解为可管理的模块（每个模块耗时2-5天）
创建任务文件的分步指南
对于每个需要创建的任务：
  1. 复制模板:
    bash
    cp [path-to-task-template.md] .plans/[feature-name]/tasks/T01.md
  2. 更新任务标题：将 
    T0X
    替换为实际任务编号（如 T01、T02 等）
  3. 填写核心部分:
    • 目标：一个清晰、可衡量的目标
    • 背景：该任务与功能及选定方案的关联
    • 需求：详细的规格说明和实施步骤
    • 行动项：具体的待完成勾选事项
  4. 更新元数据：设置状态（🟡 规划中）、工作量（小/中/大）、依赖项
  5. 添加到进度摘要：在 plan.md 中添加链接：
    - [ ] [**T01**: Task Name](tasks/T01.md) - Status: 🟡 Planned
在 TodoWrite 中标记阶段4为已完成
输出结果：tasks/ 目录下包含完整任务拆解的文件（T01.md - T0N.md），所有任务均链接到 plan.md 的进度摘要中

Phase 5: Working with Tasks (Implementation)

阶段5：任务执行（实施阶段）

Note: Phase 5 is NOT tracked in TodoWrite. Track progress directly in task files and plan.md.
IMPORTANT: Before starting work on ANY task, read 
references/task-planning-guide.md
for:
  • Task structure guidance and best practices
  • How to maintain task files during execution
  • Examples of effective task documentation
  • Common pitfalls to avoid
When to consult task-planning-guide.md:
  • Before starting a new task (every time)
  • When unclear about task file structure or what to document
  • When encountering challenges during task execution
  • When adding new tasks mid-implementation
注意：阶段5不在 TodoWrite 中跟踪。直接在任务文件和 plan.md 中跟踪进度。
重要提示：在开始任何任务前，请阅读 
references/task-planning-guide.md
以了解：
  • 任务结构指南和最佳实践
  • 执行过程中如何维护任务文件
  • 有效任务文档的示例
  • 需要避免的常见陷阱
何时查阅 task-planning-guide.md:
  • 开始新任务前（每次都要）
  • 对任务文件结构或需记录内容不明确时
  • 任务执行遇到挑战时
  • 实施过程中新增任务时

Task Execution Discipline

任务执行规范

CRITICAL RULE: Work on ONE task at a time. Do NOT start the next task until the current task is FULLY completed.
Task Status Flow:
  1. 🟡 Planned → Task created but not started
  2. 🟢 In Progress → Currently working on this task (only ONE task should be in this state)
  3. ✅ Completed → All action items done, both locations updated, Execution Summary filled
  4. 🔴 Blocked → Cannot proceed due to dependency or external issue (move to next task until unblocked)
核心规则：一次只处理一个任务。在当前任务完全完成前，请勿开始下一个任务。
任务状态流转:
  1. 🟡 规划中 → 任务已创建但未开始
  2. 🟢 进行中 → 当前正在处理该任务（同一时间只能有一个任务处于此状态）
  3. ✅ 已完成 → 所有行动项已完成，两处状态均已更新，执行摘要已填写
  4. 🔴 阻塞 → 因依赖关系或外部问题无法继续（转移到下一个非阻塞任务，直到问题解决）

Task Lifecycle: Step-by-Step

任务生命周期：分步指南

Starting a Task:
  1. Read 
    references/task-planning-guide.md
     - Review relevant sections before beginning work
  2. Choose next task from plan.md Progress Summary (respecting dependencies)
  3. Update status to 🟢 In Progress in TWO places:
    • Task file metadata: 
      **Status**: 🟢 **In Progress**
    • plan.md Progress Summary: 
      - [ ] [**T01**: Task Name](tasks/T01.md) - Status: 🟢 In Progress
During Task Execution: 4. Work through Action Items, checking off boxes as you complete them:
markdown
- [x] Create API endpoint
- [x] Add request validation
- [ ] Add error handling  ← Currently working here
- [ ] Write tests
  1. Update task file in real-time as work progresses
  2. If you discover new requirements, add them to Action Items
Completing a Task: 7. Verify ALL action items are checked: 
[x]
8. Fill in "Execution Summary" section in task file:
markdown
## Execution Summary
**Completed**: 2025-01-08 14:30

**What was implemented**:
- Added /api/users endpoint with validation
- Implemented error handling for edge cases

**Challenges encountered**:
- Had to refactor auth middleware to support new endpoint
  1. Update status to ✅ Completed in TWO places:
    • Task file metadata: 
      **Status**: ✅ **Completed**
    • plan.md Progress Summary: 
      - [x] [**T01**: Task Name](tasks/T01.md) - Status: ✅ Completed
  2. Explicitly ask user: "Task T01 is complete. Ready to move to T02?"
  3. ONLY after user confirms proceed to next task
开始任务:
  1. 阅读 
    references/task-planning-guide.md
     - 开始前回顾相关部分
  2. 从 plan.md 的进度摘要中选择下一个任务（需尊重依赖关系）
  3. 在两处更新状态为 🟢 进行中:
    • 任务文件元数据：
      **Status**: 🟢 **In Progress**
    • plan.md 进度摘要：
      - [ ] [**T01**: Task Name](tasks/T01.md) - Status: 🟢 In Progress
任务执行过程中: 4. 完成行动项，完成后勾选复选框：
markdown
- [x] Create API endpoint
- [x] Add request validation
- [ ] Add error handling  ← Currently working here
- [ ] Write tests
  1. 实时更新任务文件
  2. 如果发现新需求，添加到行动项中
完成任务: 7. 验证所有行动项均已勾选：
[x]
8. 填写任务文件中的“执行摘要”部分：
markdown
## Execution Summary
**Completed**: 2025-01-08 14:30

**What was implemented**:
- Added /api/users endpoint with validation
- Implemented error handling for edge cases

**Challenges encountered**:
- Had to refactor auth middleware to support new endpoint
  1. 在两处更新状态为 ✅ 已完成:
    • 任务文件元数据：
      **Status**: ✅ **Completed**
    • plan.md 进度摘要：
      - [x] [**T01**: Task Name](tasks/T01.md) - Status: ✅ Completed
  2. 明确询问用户：“任务T01已完成，是否可以开始T02？”
  3. 仅在用户确认后 再开始下一个任务

Dual-Tracking Example

双重跟踪示例

When completing T01, you must update BOTH locations:
In 
tasks/T01.md
 (lines 7-9):
markdown
**Status**: ✅ **Completed**
**Effort**: Medium
**Blocked By**: None
In 
plan.md
Progress Summary (line ~18):
markdown
- [x] [**T01**: Add API endpoint](tasks/T01.md) - Status: ✅ Completed
Why dual-tracking?
  • plan.md provides high-level overview of all tasks at a glance
  • Task files provide detailed implementation notes for deep dives
  • Both serve different purposes and audiences
完成T01时，必须更新两处：
在 
tasks/T01.md
中（第7-9行）:
markdown
**Status**: ✅ **Completed**
**Effort**: Medium
**Blocked By**: None
在 
plan.md
进度摘要中（约第18行）:
markdown
- [x] [**T01**: Add API endpoint](tasks/T01.md) - Status: ✅ Completed
为什么需要双重跟踪？
  • plan.md 提供所有任务的高层级概览
  • 任务文件提供详细的实施说明，用于深入查看
  • 两者服务于不同的目的和受众

Handling Blocked Tasks

处理阻塞任务

If you cannot complete a task:
  1. Update status to 🔴 Blocked in both locations
  2. Update "Blocked By" field in task file metadata
  3. Document blocking reason in task file
  4. Move to next non-blocked task
  5. Return when blocker is resolved
如果无法完成任务：
  1. 在两处更新状态为 🔴 阻塞
  2. 更新任务文件元数据中的“依赖项”字段
  3. 在任务文件中记录阻塞原因
  4. 转移到下一个非阻塞任务
  5. 阻塞问题解决后再返回

Discovering New Tasks Mid-Implementation

实施过程中发现新任务

If you discover additional work during Phase 5:
  1. Create new task file (e.g., 
    T06.md
    ) in tasks/ directory
  2. Fill in all sections using task-template.md
  3. Add link to plan.md Progress Summary
  4. Update dependent tasks if needed
Remember: ONE task at a time. Complete it FULLY (all checkboxes, both locations updated, Execution Summary filled), then ASK USER for confirmation before moving to the next.
如果在阶段5发现额外工作：
  1. 在 tasks/ 目录下创建新的任务文件（如 
    T06.md
    ）
  2. 使用 task-template.md 填写所有部分
  3. 在 plan.md 进度摘要中添加链接
  4. 如有需要，更新相关依赖任务
请记住：一次只处理一个任务。确保完全完成（所有复选框勾选、两处状态更新、执行摘要填写），然后询问用户确认后再开始下一个任务。

Phase 6: Post-Implementation Review

阶段6：实施后评审

Note: Phase 6 is NOT tracked in TodoWrite. Update the plan document directly.
After feature completion:
  • Fill in "Lessons Learned" section
  • Verify all task statuses are accurate
  • Document any technical debt or future work
  • Review what went well and what could improve
注意：阶段6不在 TodoWrite 中跟踪。直接更新规划文档。
功能完成后：
  • 填写“经验教训”部分
  • 验证所有任务状态准确无误
  • 记录任何技术债务或未来工作
  • 回顾工作中的亮点与待改进点

Workflow Summary

工作流程摘要

TodoWrite tracks ONLY phases 1-4 (not subtasks):
- [ ] Phase 1: Setup template with Research section
- [ ] Phase 2: Conduct research and iterate with user
- [ ] Phase 3: Finalize selected approach
- [ ] Phase 4: Create implementation tasks (T01-T0N)
Phase-by-Phase Workflow:
  1. Phase 1 - Setup:
    • Create 
      .plans/[feature-name]/
      and 
      .plans/[feature-name]/tasks/
      directories
    • Copy plan-template.md to 
      .plans/[feature-name]/plan.md
    • Create Research section ONLY in plan.md
    • DO NOT create T01, T02, T03 task files yet
    • Mark Phase 1 complete in TodoWrite
  2. Phase 2 - Research & Iterate (AskUserQuestion REQUIRED):
    • Explore codebase, document findings in plan.md
    • Present 2-3 approach options
    • Iterate on EACH proposal via AskUserQuestion (discuss trade-offs, clarify constraints)
    • User may correct assumptions - update research
    • If user strongly prefers one approach, may skip detailed discussion of remaining options
    • Proactively ask: "Are you ready to select an approach?"
    • Mark Phase 2 complete when user confirms
  3. Phase 3 - Finalize:
    • Present 2-3 researched approaches and ask user to select one
    • Once user confirms, fill "Selected Approach" section in plan.md
    • Mark research as ✅ Completed in plan.md
    • Mark Phase 3 complete once documentation is done
  4. Phase 4 - Create Tasks:
    • Read 
      references/task-planning-guide.md
      before creating tasks
    • NOW create T01.md, T02.md, T03.md, ...T0N.md files in 
      .plans/[feature-name]/tasks/
    • Copy task-template.md for each task file
    • Fill in task details based on selected approach
    • Number of tasks depends on complexity
    • Update Progress Summary in plan.md with links to task files
    • Mark Phase 4 complete in TodoWrite
  5. Phase 5 - Implementation (ONE task at a time):
    • Read 
      references/task-planning-guide.md
      before starting EACH task
    • Work on ONE task until FULLY completed (all checkboxes, both locations updated, Execution Summary filled)
    • Update status in TWO places: task file metadata AND plan.md Progress Summary
    • Track progress: 🟡 Planned → 🟢 In Progress → ✅ Completed
    • Check off action items as you complete them
    • Fill Execution Summary before marking complete
    • Explicitly ask user for confirmation before moving to next task
    • ONLY after user confirms proceed to next task
  6. Phase 6 - Review:
    • Document lessons learned in plan.md
TodoWrite 仅跟踪阶段1-4（不跟踪子任务）：
- [ ] Phase 1: Setup template with Research section
- [ ] Phase 2: Conduct research and iterate with user
- [ ] Phase 3: Finalize selected approach
- [ ] Phase 4: Create implementation tasks (T01-T0N)
分阶段工作流程:
  1. 阶段1 - 准备:
    • 创建 
      .plans/[feature-name]/
      和 
      .plans/[feature-name]/tasks/
      目录
    • 将 plan-template.md 复制到 
      .plans/[feature-name]/plan.md
    • 仅在 plan.md 中创建调研部分
    • 不要提前创建 T01、T02、T03 等任务文件
    • 在 TodoWrite 中标记阶段1为已完成
  2. 阶段2 - 调研与迭代（必须使用 AskUserQuestion）:
    • 探索代码库，在 plan.md 中记录调研结果
    • 呈现2-3种方案选项
    • 针对每个方案通过 AskUserQuestion 迭代沟通（讨论权衡、明确约束）
    • 用户可能会纠正你的假设 - 更新调研内容
    • 如果用户明确偏好某一方案，可跳过对剩余方案的详细讨论
    • 主动询问：“你是否已准备好选定方案？”
    • 用户确认后标记阶段2为已完成
  3. 阶段3 - 最终确定:
    • 呈现2-3种调研得出的方案，请用户选定
    • 用户确认后，在 plan.md 中填写“选定方案”部分
    • 在 plan.md 中标记调研为 ✅ 已完成
    • 文档填写完成后标记阶段3为已完成
  4. 阶段4 - 创建任务:
    • 创建任务文件前请阅读 
      references/task-planning-guide.md
    • 现在在 
      .plans/[feature-name]/tasks/
      目录下创建 T01.md、T02.md、T03.md...T0N.md 文件
    • 为每个任务文件复制 task-template.md
    • 根据选定方案填写任务详情
    • 任务数量取决于复杂度
    • 在 plan.md 的进度摘要中添加任务文件链接
    • 在 TodoWrite 中标记阶段4为已完成
  5. 阶段5 - 实施（一次一个任务）:
    • 开始每个任务前请阅读 
      references/task-planning-guide.md
    • 一次只处理一个任务，直到完全完成（所有复选框勾选、两处状态更新、执行摘要填写）
    • 在两处更新状态：任务文件元数据 和 plan.md 进度摘要
    • 跟踪进度：🟡 规划中 → 🟢 进行中 → ✅ 已完成
    • 完成行动项后勾选复选框
    • 标记完成前填写执行摘要
    • 明确询问用户确认后再开始下一个任务
    • 仅在用户确认后才继续下一个任务
  6. 阶段6 - 评审:
    • 在 plan.md 中记录经验教训

Key Patterns from Successful Use

成功实践的关键模式

Pattern 1: Follow Existing Patterns

模式1：遵循现有模式

During research phase, research existing similar features and match their architecture exactly. Benefit: Consistent codebase, faster implementation, reduced bugs.
在调研阶段，研究现有类似功能并完全匹配其架构。 优势：代码库一致性、实施速度更快、减少bug。

Pattern 2: Simplify When Possible

模式2：尽可能简化

During research, look for ways to simplify (e.g., avoid unnecessary API calls). Benefit: Reduced dependencies, better performance, easier maintenance.
在调研阶段，寻找简化方式（例如：避免不必要的API调用）。 优势：减少依赖、性能更好、维护更简单。

Pattern 3: Discover Existing Implementations

模式3：发现已有的实现

Research phase may reveal the work is already done - mark task complete. Benefit: Avoids duplicate work, leverages tested code.
调研阶段可能会发现工作已完成 - 标记任务为已完成。 优势：避免重复工作、利用经过测试的代码。

Pattern 4: Document Design Decisions

模式4：记录设计决策

During research phase, use the "Selected Approach" section to document WHY you chose one approach over alternatives. Include: decision, rationale, key findings, and implementation plan. Benefit: Future developers understand rationale, prevents second-guessing, provides clear starting point.
在调研阶段，使用**“选定方案”**部分记录为何选择某一方案而非其他方案。 内容包括：决策、理由、关键发现和实施计划。 优势：未来开发者能理解决策依据、避免反复纠结、提供清晰的起点。

Pattern 5: Keep Tasks Focused

模式5：保持任务聚焦

Break large tasks into smaller chunks that are independently testable. Benefit: Steady progress, clear milestones, easier to parallelize.
将大型任务拆解为可独立测试的较小模块。 优势：进度稳定、里程碑清晰、易于并行处理。

Reference Materials

参考资料

CRITICAL: 
references/task-planning-guide.md
is NOT just for planning - read it throughout implementation.
Read 
references/task-planning-guide.md
:
  • Phase 4: Before creating task files (understand task structure, sizing, dependencies)
  • Phase 5: Before starting EACH task (review best practices, avoid common pitfalls)
  • During execution: When updating task files, adding action items, or documenting progress
  • When stuck: Consult checklist for good task planning and common pitfalls section
Remember:
  1. TodoWrite tracks PHASES - not individual subtasks
  2. Phases are sequential - complete Phase 1 before Phase 2, etc.
  3. Phase 2 is iterative - use AskUserQuestion multiple times, expect back-and-forth
  4. User confirms approach - do NOT fill "Selected Approach" until user confirms
  5. No premature planning - T01-T0N created in Phase 4
  6. Task count is flexible - create as many as needed (T01, T02, ...T0N)
  7. ONE task at a time - Complete current task FULLY (all checkboxes, both locations, Execution Summary) before starting next
  8. Dual-tracking required - Update status in BOTH task file AND plan.md
  9. Explicit user confirmation - Ask user for approval before moving to next task
  10. Read task-planning-guide.md - Before Phase 4, before EACH task in Phase 5, and when stuck
关键提示：
references/task-planning-guide.md
不仅用于规划 - 整个实施过程中都要阅读。
何时阅读 
references/task-planning-guide.md
:
  • 阶段4：创建任务文件前（了解任务结构、规模、依赖关系）
  • 阶段5：开始每个任务前（回顾最佳实践、避免常见陷阱）
  • 执行过程中：更新任务文件、添加行动项或记录进度时
  • 遇到问题时：查阅良好任务规划的检查清单和常见陷阱部分
请记住:
  1. TodoWrite 跟踪阶段 - 不跟踪单个子任务
  2. 阶段是顺序执行的 - 完成阶段1后再进入阶段2，以此类推
  3. 阶段2是迭代式的 - 多次使用 AskUserQuestion，预计会有来回沟通
  4. 用户确认方案 - 直到用户确认后才能填写“选定方案”部分
  5. 不要提前规划 - T01-T0N 在阶段4创建
  6. 任务数量灵活 - 根据需要创建（T01、T02...T0N）
  7. 一次一个任务 - 当前任务完全完成（所有复选框、两处状态、执行摘要）后再开始下一个
  8. 必须双重跟踪 - 在任务文件 和 plan.md 中都更新状态
  9. 明确的用户确认 - 开始下一个任务前请用户批准
  10. 阅读 task-planning-guide.md - 阶段4前、阶段5的每个任务前，以及遇到问题时