Executing Plans

Core principle: Batch execution with checkpoints for review.

its-d updated 1mo ago
Claude CodeGeneric
View source ↗
# /executing-plans

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

**Core principle:** Batch execution with checkpoints for review.

**Announce at start:** "I'm using /executing-plans to implement this plan."

## 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 before starting
4. If no concerns: 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. Run verifications as specified
4. Mark as completed

### 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 and verified:
- Announce: "I'm using /finishing-a-development-branch to complete this work."
- Run /finishing-a-development-branch
- Follow that command to verify tests, present options, execute choice

## 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:**
- Plan is updated based on your feedback
- Fundamental approach needs rethinking

**Don't force through blockers** — stop and ask.

## Remember
- Review plan critically first
- Follow plan steps exactly
- Don't skip verifications
- Between batches: just report and wait
- Stop when blocked, don't guess
- Never start implementation on main/master branch without explicit user consent

## Integration
**Required workflow:**
- **Run /using-git-worktrees first** — set up isolated workspace before starting
- **/writing-plans** — creates the plan this command executes
- **/finishing-a-development-branch** — complete development after all tasks

Maintain Executing Plans?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[Executing Plans on getagentictools](https://getagentictools.com/loops/its-d-executing-plans?ref=badge)
npx agentictools info loops/its-d-executing-plans

The second line is the CLI lookup for this page — handy in READMEs and docs.