execute

name	execute
description	Execute an implementation plan
argument-hint	[plan-file]

Execute: Implement from Plan

Plan to Execute

Read plan file: $ARGUMENTS

Execution Instructions

1. Read and Understand

• Read the ENTIRE plan carefully
• Understand all tasks and their dependencies
• Note the validation commands to run
• Review the testing strategy

2. Execute Tasks in Order

For EACH task in "Step by Step Tasks":

a. Navigate to the task

• Identify the file and action required
• Read existing related files if modifying

b. Implement the task

• Follow the detailed specifications exactly
• Maintain consistency with existing code patterns
• Include proper type hints and documentation
• Add structured logging where appropriate

c. Verify as you go

• After each file change, check syntax
• Ensure imports are correct
• Verify types are properly defined

3. Implement Testing Strategy

After completing implementation tasks:

• Create all test files specified in the plan
• Implement all test cases mentioned
• Follow the testing approach outlined
• Ensure tests cover edge cases

4. Run Validation Commands

Execute ALL validation commands from the plan in order:

# Run each command exactly as specified in plan

If any command fails:

• Fix the issue
• Re-run the command
• Continue only when it passes

5. Final Verification

Before completing:

• All tasks from plan completed
• All tests created and passing
• All validation commands pass
• Code follows project conventions
• Documentation added/updated as needed

6. Archive the Completed Plan

After successful verification:

• Move the plan file to plans/archive/ (create the directory if it doesn't exist)
• Example: plans/2026-03-01-feature.md -> plans/archive/2026-03-01-feature.md
• Active plans/ should only contain pending or in-progress plans

Output Report

Provide summary:

Completed Tasks

• List of all tasks completed
• Files created (with paths)
• Files modified (with paths)

Tests Added

• Test files created
• Test cases implemented
• Test results

Validation Results

# Output from each validation command

Ready for Commit

• Confirm all changes are complete
• Confirm all validations pass
• Ready for /commit command

Notes

• If you encounter issues not addressed in the plan, document them
• If you need to deviate from the plan, explain why
• If tests fail, fix implementation until they pass
• Don't skip validation steps