aile-executing-plans

Aile: Test-Driven Development

Overview

Load the plan, review rigorously, execute tasks in batches, and report reviews between batches.

Core principles: Batch execution with checkpoints for architect review.

The goal is not "writing tests", but ratherusing runnable evidence to prove that the behavior is implemented as planned, and to correspond one-to-one with the Phase 2 plan (docs/plans/{Story-Key}/analysis.md and docs/plans/{Story-Key}/plan.md / plan-{序号}.md).

Workflow overview

项目初始化：project-docs-init（创建文档）
      ↓
需求分析：aile-requirement-analysis（结构化需求分析  + 更新文档）
      ↓
计划制定：aile-writing-plans（设计 + 计划）
      ↓
执行开发：aile-executing-plans 或 aile-subagent-dev（按计划执行 + 人工检查点）
      ↓
交付总结：aile-delivery-report（整理交付材料 + 回链 Story）

Execution flow

Step 1: Load and review the plan

1. Read the plan file, identify docs/plans/{Story-Key}/ under plan.md and plan-{序号}.md
2. Select the execution plan file:
   • If the user explicitly specifies a plan file: execute according to the specified file
   • If not specified and plan-{序号}.mdexists: use the file with the largest number (e.g. plan-3.md takes priority over plan-2.md）
   • If no plan-{序号}.mdexists: use plan.md
   • If none of the above files exist: stop immediately and request a supplementary plan file
3. Review critically - identify any problems or concerns about the plan
4. If there are concerns: raise these issues with your human partner before starting
5. If there are no issues: create TodoWrite and continue

Step 2: Execute batch processing

Default: the first 3 tasks

For each task:

1. Mark as in progress
2. Strictly follow each step (the plan has small steps)
3. Run verification as specified
4. Mark as completed

Step 3: Report

After the batch is complete:

• Show what has been implemented
• Show the verification output
• Say: "Ready for feedback."

Step 4: Continue

Based on feedback:

• Apply changes if needed
• Execute the next batch
• Repeat until complete

Step 5: Commit Git changes (requires explicit user request)

After each batch of tasks passes verification and receives feedback confirmation, one commit may be made:

• Execute only when the user explicitly requests "commit code/commit changes" git commit
• Before committing, check the scope of changes to avoid mixing in unrelated files:
  • git status
  • git add <本批次相關檔案>
  • git status
• Recommended commit message template:feat({Story-Key}): complete batch {n} or fix({Story-Key}): complete batch {n}
• Example commit command:git commit -m "feat({Story-Key}): complete batch {n}"
• Without explicit user request, do not execute git push

Step 6: Complete development

After all tasks are completed and verified:

• Announce: "I am using the aile-delivery-report skill to complete delivery wrap-up."
• Required sub-skills: Use superpower: aile-delivery-report
• Follow that skill to verify tests, present options, and execute the selection

When to stop and ask for help

Stop execution immediately in the following situations:

• Encountering an obstacle in a batch (missing dependency, test failure, unclear instruction)
• The plan has major flaws and cannot be started
• You do not understand the instruction
• Verification failed multiple times

**Ask for clarification instead of guessing. **

When to revisit previous steps

Return to review (Step 1) in the following cases:

• The partner updates the plan based on your feedback
• The basic approach needs to be rethought

Do not force your way 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
• If blocked, stop; do not guess randomly
• Never start implementation on the main/master branch without the user's explicit consent

All-in-one

Required workflow skills:

• Superpowers: aile-writing-plans - Create the plan that this skill executes
• Superpowers: aile-delivery-report - Enter delivery wrap-up after completing all tasks