executing-plans

Executing Plans - Execute Implementation Plans in Batches

Skill Overview

Executing Plans is a specialized skill for executing written implementation plans. By using batched execution and checkpoint review mechanisms, it ensures large-scale development programs proceed in an orderly manner and receive timely feedback from the architect.

Applicable Scenarios

You have a written implementation plan that needs to be executed

Use this skill when you have completed planning and written a detailed implementation plan (the Plan file) and need to execute it in a separate session according to the plan.

You need to implement step-by-step in batches

For large development tasks consisting of multiple steps, this is suitable for scenarios where you need to execute in batches and perform review and feedback after each batch.

You need an architect to review and steer execution

During execution, checkpoints should be set so that the architect or team lead can review progress and guide direction.

Core Functions

Batched execution with a checkpoint mechanism

By default, each batch executes 3 tasks. After completing them, the implementation results and verification outputs are presented. Then execution pauses for feedback before moving on to the next batch, ensuring the direction is correct.

Critical review of the plan before execution

Before starting, the plan is reviewed to identify potential issues or questions. If there are concerns, they will be raised before execution to avoid carrying out an incorrect plan.

Blocking handling and help-seeking mechanism

If you encounter blockers such as missing dependencies, test failures, unclear instructions, or repeated verification failures, stop immediately and seek help instead of guessing blindly.

Common Questions

What scenarios is executing-plans suitable for?

When you have a written implementation plan file that you need to execute in a dedicated development session, and you want to progress in batches while receiving review feedback between batches, this skill is the best choice. It is especially suitable for medium-to-large feature development, refactoring projects, or architecture upgrade initiatives.

How many tasks are handled per batch?

By default, each batch handles 3 tasks. This number balances execution efficiency with review and feedback. You can adjust the batch size in coordination with your team based on actual circumstances.

When should execution be stopped?

Execution should be stopped immediately and help should be sought in the following situations: missing dependencies, test failures, unclear instructions, repeated verification failures, a serious flaw in the plan that prevents starting, or when you do not understand a given instruction. Stopping and asking is more efficient than making blind guesses.