What happens if a task in the plan fails?

The skill will mark the task as FAILED [!] in the plan file, allowing you to see exactly where the process was interrupted.

Can I use this for complex software migrations?

Yes, it is specifically designed for multi-stage tasks where tracking progress and ensuring no steps are missed is essential.

How does the skill track progress?

It updates the status indicators in your plan file from PENDING [ ] to IN_PROGRESS [~] and finally to DONE [x] or FAILED [!] as it works.

Does Claude verify all tasks are finished?

Yes, the final step of the skill involves re-reading the entire plan file to verify that every single task has been marked as DONE.

What file format does this skill require?

The skill works with Markdown (.md) files typically located in a /plans directory, following a specific naming convention like {date}-{name}-{version}.md.

Execute Plan

Name: Execute Plan
Author: jhoshim89

byjhoshim89

Productivity & Workflow

Automates the execution of structured task plans with real-time status tracking and progress updates within Markdown files.

About

The Execute Plan skill enables Claude to methodically work through complex, multi-step projects by following a pre-defined plan file. It ensures high reliability by requiring a verbal commitment to complete all tasks and maintains a clear audit trail by updating task statuses (Pending, In Progress, Done, Failed) directly within the plan's Markdown file. This skill is particularly useful for developers managing intricate refactors, migrations, or any workflow where ensuring 100% completion of a checklist is critical.

Key Features

Mandatory commitment ritual to ensure all plan items are addressed
Final verification step to confirm completion of all sub-tasks
0 GitHub stars
Automatic status tracking using standard Markdown indicators
Sequential task execution with real-time file updates
Standardized plan file naming for organized project history

Use Cases

Executing step-by-step software deployment or migration procedures
Automating complex maintenance routines with built-in accountability
Managing large-scale codebase refactoring involving multiple files

About

Key Features

Mandatory commitment ritual to ensure all plan items are addressed
Final verification step to confirm completion of all sub-tasks
0 GitHub stars
Automatic status tracking using standard Markdown indicators
Sequential task execution with real-time file updates
Standardized plan file naming for organized project history

Use Cases

Executing step-by-step software deployment or migration procedures
Automating complex maintenance routines with built-in accountability
Managing large-scale codebase refactoring involving multiple files