execute

name	execute
description	Plan execution methodology and verification strategies. Triggers on: "execute plan", "implement plan", "run plan", "follow the plan", "start implementation", "continue execution", "resume plan". Provides execution patterns, progress tracking, and error handling strategies.

Plan Execution Skill

Guidelines for executing implementation plans effectively.

Execution Principles

1. Follow Exactly - Do what the plan says, nothing more
2. Verify Always - Run verification after each task
3. Track Progress - Update plan file continuously
4. Ask When Stuck - Report blockers, don't guess

Execution Workflow

1. Load Plan

• Read plan from .claude/plans/
• Validate structure and status
• Check prerequisites
• Identify resume point if partially complete

2. Pre-Execution Checks

• Plan status is "approved" or "in_progress"
• All dependencies available
• Test framework ready (for TDD)

3. Execute Tasks

For each task:

1. Announce task start
2. Execute action
3. Run verification
4. Update status
5. Report result

4. Phase Transitions

• Summarize completed phase
• Run phase-level verification
• Ask user before continuing

Task Actions

Create

• Use Write tool for new files
• Follow project conventions
• Include all required code

Modify

• Use Edit tool for changes
• Prefer precise edits over rewrites
• If Serena available, use replace_symbol_body()

Delete

• Confirm with user first
• Consider backup for significant files

Run

• Execute via Bash tool
• Capture and report output
• Check exit code

Verification Patterns

# Command verification
[command] && echo "PASSED" || echo "FAILED"

# File verification
test -f [path] && echo "File exists"

# Test verification
php artisan test --filter=[Test]
flutter test [file]
npm run test -- [file]

Error Handling

Task Failure

• Stop immediately
• Report error with details
• Ask: (r)etry, (s)kip, (m)odify, (a)bort

Verification Failure

• Report expected vs actual
• Ask: (i)nvestigate, (p)roceed

Blocker Found

• Document in plan progress
• Report to user
• Wait for guidance

Progress Tracking

Update plan file after each task:

## Progress

### Session [timestamp]
- Task 1.1: COMPLETED
- Task 1.2: COMPLETED - Note: [any notes]
- Task 2.1: IN_PROGRESS

Update task status inline:

- **Status**: pending → completed

Reference

For execution rules and patterns, see references/execution-rules.md.