Back to Details

aile-executing-plans

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Aile：测试驱动开发

Aile: Test-Driven Development

概述

Overview

加載計劃，嚴格審查，分批執行任務，報告批間審查。
核心原則： 帶有檢查點的批量執行，以供架構師審查。
目标不是“写了测试”，而是用可运行证据证明行为按计划实现，并与阶段 2 的计划（
docs/plans/{Story-Key}/analysis.md
和 
docs/plans/{Story-Key}/plan.md
）一一对应。
Load the plan, conduct strict reviews, execute tasks in batches, and report for inter-batch reviews.
Core Principle: Batch execution with checkpoints for architect review.
The goal is not "writing tests", but proving with runnable evidence that behaviors are implemented as planned, and it must correspond one-to-one with the Phase 2 plans (
docs/plans/{Story-Key}/analysis.md
and 
docs/plans/{Story-Key}/plan.md
).

执行流程

Execution Process

第 1 步：載入並審查計劃

Step 1: Load and Review the Plan

  1. 讀取計劃文件（
    docs/plans/{Story-Key}/plan.md
    ）
  2. 批判性地審查 - 找出有關計劃的任何問題或疑慮
  3. 如果有疑慮：在開始之前與您的人類伴侶提出這些問題
  4. 如果沒有問題：創建 TodoWrite 並繼續
  1. Read the plan file (
    docs/plans/{Story-Key}/plan.md
    )
  2. Conduct a critical review - identify any issues or concerns about the plan
  3. If there are concerns: Raise these questions with your human partner before starting
  4. If there are no issues: Create a TodoWrite and proceed

步驟2：執行批次處理

Step 2: Execute Batch Processing

預設：前 3 個任務
對於每個任務：
  1. 標記為進行中
  2. 嚴格遵循每個步驟（計劃有小步驟）
  3. 按規定運行驗證
  4. 標記為已完成
Default: First 3 tasks
For each task:
  1. Mark it as in progress
  2. Strictly follow each step (the plan has small steps)
  3. Run the verification as specified
  4. Mark it as completed

第三步：報告

Step 3: Report

批次完成後：
  • 顯示已實施的內容
  • 顯示驗證輸出
  • 說：“準備好接受反饋。”
After completing a batch:
  • Show what has been implemented
  • Show the verification output
  • Say: "Ready for feedback."

第 4 步：繼續

Step 4: Continue

根據回饋：
  • 如果需要，應用更改
  • 執行下一批
  • 重複直到完成
Based on feedback:
  • Apply changes if needed
  • Execute the next batch
  • Repeat until completion

第五步：完成開發

Step 5: Complete Development

所有任務完成並驗證後：
  • 宣佈：“我正在使用完成開發分支技能來完成這項工作。”
  • 所需的子技能： 使用超能力：完成開發分支
  • 遵循該技能來驗證測試、呈現選項、執行選擇
After all tasks are completed and verified:
  • Announce: "I am using the Complete Development Branch skill to finish this work."
  • Required Sub-skills: Superpower: Complete Development Branch
  • Follow that skill to verify tests, present options, and execute selections

何時停下來尋求幫助

When to Stop and Ask for Help

在以下情況下立即停止執行：
  • 在批次中遇到阻礙（缺少依賴性、測試失敗、指令不清楚）
  • 計劃存在重大缺陷，無法啟動
  • 你不明白指令
  • 驗證多次失敗
**要求澄清而不是猜測。 **
Stop execution immediately in the following cases:
  • Encounter obstacles in the batch (missing dependencies, test failures, unclear instructions)
  • The plan has major flaws that prevent initiation
  • You do not understand the instructions
  • Verification fails multiple times
**Ask for clarification instead of guessing. **

何時重新審視之前的步驟

When to Revisit Previous Steps

在以下情況下返回審核（步驟 1）：
  • 合作夥伴根據您的反饋更新計劃
  • 基本方法需要重新思考
不要強行通過阻礙 - 停下來詢問。
Return to review (Step 1) in the following cases:
  • The partner updates the plan based on your feedback
  • The basic approach needs rethinking
Do not force through obstacles - stop and ask.

記住

Remember

  • 首先嚴格審查計劃
  • 嚴格遵循計劃步驟
  • 不要跳過驗證
  • 計劃中提到的參考技能
  • 批次之間：只需報告並等待
  • 堵住就停下來，別亂猜
  • 未經使用者明確同意，切勿在主/主分支上開始實施
  • First, strictly review the plan
  • Strictly follow the plan steps
  • Do not skip verification
  • Reference skills mentioned in the plan
  • Between batches: Just report and wait
  • Stop when stuck, do not guess
  • Never start implementation on the main/master branch without explicit user consent

一體化

Integration

所需的工作流程技能：
  • 超級能力：使用-git-worktrees - 必需：在開始之前設置隔離的工作區
  • 超級大國：寫作計劃 - 創建該技能執行的計劃
  • 超級大國：完成開發分支 - 在完成所有任務後完成開發
Required Workflow Skills:
  • Superpower: Use-git-worktrees - Required: Set up an isolated workspace before starting
  • Superpower: Writing Plan - Create the plan that this skill executes
  • Superpower: Complete Development Branch - Complete development after all tasks are done