aile-executing-plans

Original：🇨🇳 Chinese
Translated

TDD Skill for Team Workflows (Phase 3). Before writing any implementation code, you must first write a failing test and verify the failure, then write the minimal implementation until it passes, and finally refactor and re-test.

1installs
Sourcezhucl1006/ailesuperpowers
Added on

NPX Install

npx skill4agent add zhucl1006/ailesuperpowers aile-executing-plans

Tags

Translated version includes tags in frontmatter
test-driven-developmentteam-workflowbatch-executioncode-verificationgit-worktrees

SKILL.md Content (Chinese)

View Translation Comparison →

Aile: Test-Driven Development

Overview

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

Step 1: Load and Review the Plan

  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

Step 2: Execute Batch Processing

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."

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

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

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