AgentSkillsCN

executing-plans

当您已经制定了书面实施计划，可在后续单独的会议中执行，并设置审核节点时，可使用此方法。

SKILL.md
--- frontmatter
name: executing-plans
description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
user-invocable: false

Executing Plans

Overview

Load plan, review critically, execute tasks in batches, report for review between batches.

Core principle: Batch execution with checkpoints for architect review.

The Process

Step 1: Load and Review Plan

  1. •Read plan file
  2. •Review critically - identify any questions or concerns about the plan
  3. •If concerns: Raise them with your human partner before starting
  4. •If no concerns: Create TodoWrite and proceed

Step 2: Execute Batch

Default: First 3 tasks

For each task:

  1. •Mark as in_progress
  2. •Follow each step exactly (plan has bite-sized steps)
  3. •VERIFY BEFORE COMMIT:
    • •TDD mode: Run tests, ensure they pass
    • •Non-TDD mode: Execute the verification method specified in plan header
  4. •REQUIRED SKILL: Use code-simplifier
  5. •Commit only after verification passes
  6. •Mark as completed

Important: Never commit unverified work. If verification fails, fix before committing.

Step 3: Report

When batch complete:

  • •Show what was implemented
  • •Show verification output
  • •Say: "Ready for feedback."

Step 4: Continue

Based on feedback:

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

Step 5: Complete Development

After all tasks complete:

  1. •Run tests if configured on the project (check for test scripts in package.json)
  2. •Fix any failing tests before proceeding
  3. •Inform the user: "Implementation complete. All tasks executed and verified."

When to Stop and Ask for Help

STOP executing immediately when:

  • •Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
  • •Plan has critical gaps preventing starting
  • •You don't understand an instruction
  • •Verification fails repeatedly

Ask for clarification rather than guessing.

When to Revisit Earlier Steps

Return to Review (Step 1) when:

  • •Partner updates the plan based on your feedback
  • •Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Required Skills

  • •REQUIRED SKILL: Use code-simplifier before committing to simplify and clean up code

Remember

  • •Review plan critically first
  • •Follow plan steps exactly
  • •Don't skip verifications
  • •Reference skills when plan says to
  • •Between batches: just report and wait
  • •Stop when blocked, don't guess