Marketplace executing-plans

Execute implementation plans with batch processing and review checkpoints. Use when given a plan document.

install

source · Clone the upstream repo

git clone https://github.com/aiskillstore/marketplace

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/dmjgilbert/executing-plans" ~/.claude/skills/aiskillstore-marketplace-executing-plans-802e74 && rm -rf "$T"

manifest: skills/dmjgilbert/executing-plans/SKILL.md

source content

Executing Plans

Execute implementation plans systematically with quality gates between batches.

When to Use

When given a plan document to implement
After writing-plans skill produces a plan
For batch execution with human checkpoints

The Five-Step Process

Step 1: Load and Review Plan

Read the plan document carefully
Identify potential issues or ambiguities
Raise concerns with user before beginning work
Create TodoWrite with all tasks if plan seems sound

If issues found: Stop and clarify before proceeding

Step 2: Execute Batch

Default batch size: 3 tasks

For each task in batch:

Update status to
```
in_progress
```
Execute each step as written
Run specified verifications
Mark as
```
completed
```
only when verified

Step 3: Report

After completing a batch:

## Batch Complete

**Tasks Completed:** [List]

**Verifications:**

- Task 1: [Pass/Fail] - [Details]
- Task 2: [Pass/Fail] - [Details]
- Task 3: [Pass/Fail] - [Details]

**Issues Found:** [If any]

Ready for feedback.

Step 4: Continue

Incorporate any requested changes
Execute next batch
Repeat cycle

Step 5: Complete Development

After all tasks finished and verified:

Run full test suite
Announce completion
Transition to finishing workflow (merge/PR decision)

Critical Rules

STOP Immediately When:

Blockers (missing dependencies, failed tests)
Plan gaps preventing progress
Unclear instructions
Repeated verification failures (2+ on same task)

When blocked: Ask for clarification, don't force through.

Return to Step 1 When:

User updates the plan
Approach needs fundamental revision
Architecture issues discovered

Never:

Skip verifications
Force through blockers
Batch completions (mark done one at a time)
Proceed with unresolved critical issues

Batch Size Guidelines

Scenario	Batch Size
Simple tasks	3-5
Complex tasks	1-2
High-risk changes	1
User preference	As specified

Integration with Other Skills

test-driven-development: Each task follows TDD
systematic-debugging: If tests fail, use debugging skill
code-review: Request review after significant batches