What is the difference between parallel and sequential execution?

Parallel execution runs up to 2 tasks concurrently via subagents to save time, while sequential mode handles tasks one-by-one for simpler plans or work that cannot be parallelized.

How does the skill decide which execution mode to use?

The skill automatically checks for a manifest.json file in your plans directory. If it exists, parallel mode is used; otherwise, it defaults to sequential mode.

Can I stop the execution if something goes wrong?

Yes. The skill is programmed to stop immediately if it hits a blocker, fails a verification test, or if instructions are unclear. It also pauses for your feedback between every batch.

How do I ensure my plan is ready for parallel execution?

It is recommended to run the /cc:parse-plan command first to decompose plans with 4 or more tasks into a manifest.json file.

Executing Plans

Name: Executing Plans
Author: seanGSISG

byseanGSISG

Productivity & Workflow

Implements complex development plans through managed batch execution and systematic human-in-the-loop review checkpoints.

About

The Executing Plans skill provides a structured framework for Claude to carry out multi-step implementation plans with high precision and safety. By analyzing a project's task manifest, it automatically switches between parallel subagent execution for speed and sequential processing for simplicity. The skill enforces a review-first mentality, requiring a critical evaluation of the plan before execution begins and establishing mandatory checkpoints after each task batch to ensure quality and architectural alignment.

Key Features

Intelligent batching (default 3 tasks) with mandatory review gates
Significant context reduction per task to improve accuracy
Parallel subagent orchestration for up to 40% faster implementation
Automatic execution mode detection based on manifest.json availability
Seamless integration with development branch finalization workflows
0 GitHub stars

Use Cases

Managed implementation of architect-designed plans with strict quality gates
Accelerating complex development timelines through concurrent subagent execution
Executing large-scale feature migrations that require multiple coordinated sub-tasks

About

Key Features

Intelligent batching (default 3 tasks) with mandatory review gates
Significant context reduction per task to improve accuracy
Parallel subagent orchestration for up to 40% faster implementation
Automatic execution mode detection based on manifest.json availability
Seamless integration with development branch finalization workflows
0 GitHub stars

Use Cases

Managed implementation of architect-designed plans with strict quality gates
Accelerating complex development timelines through concurrent subagent execution
Executing large-scale feature migrations that require multiple coordinated sub-tasks