Executing plans

Skill a-ariff/ariff-claude-plugins/plugins/executing-plans/skills/executing-plans

65 plugins that turn Claude Code into an autonomous development team. 24 agents, 34 skills, 5 hooks. Includes 12-plugin anti-hallucination suite. One-line install.

Install

npx -y skills add a-ariff/ariff-claude-plugins --skill executing-plans

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Execute implementation plans in batches with review checkpoints

SKILL.md

2.1 KB, as published. Nobody here has run it

Executing Plans

Purpose

Execute plans in controlled batches with verification gates.

"I'm using the Executing Plans skill to implement this plan."

The Process

Load Plan → Review → Execute Batch → Report → Feedback → Next Batch

Step 1: Load & Review

Read the plan file
Review critically - identify concerns
If concerns → Raise with user before starting
Create TodoWrite for all tasks

Step 2: Execute Batch

Default batch size: 3 tasks

For each task:

Mark as in_progress
Follow each step exactly
Run verifications as specified
Mark as completed

Step 3: Report

After each batch:

## Batch Complete

**Implemented:**
- Task 1: [summary]
- Task 2: [summary]
- Task 3: [summary]

**Verification:**
\`\`\`
[test output]
\`\`\`

Ready for feedback.

Step 4: Continue

Based on feedback:

Apply changes if needed
Execute next batch
Repeat until complete

When to STOP

🛑 Stop immediately when:

Hit a blocker (missing dependency, unclear instruction)
Test fails unexpectedly
Plan has gaps preventing progress
You don't understand something

Ask for clarification. Don't guess.

Verification Rules

Before marking ANY task complete:

Run the verification command
Read the FULL output
Confirm it matches expectations
Only THEN mark complete

No "should work" or "looks good" - actual verification output.

Batch Reporting Format

### Batch N Complete

| Task | Status | Verification |
|------|--------|--------------|
| Task X | ✅ | 12/12 tests pass |
| Task Y | ✅ | Build successful |
| Task Z | ⚠️ | Needs review |

**Next batch:** Tasks A, B, C

Continue?

Completion

After all tasks:

Run full test suite
Verify all requirements met
Report final status
Hand off to finishing-branch skill if applicable