Does it verify that all tasks are finished?

Yes, the skill includes a mandatory final verification step where it re-reads the entire plan file to ensure no tasks were skipped before announcing completion.

What file format does the Plan Executor skill use?

It uses structured Markdown files located in a 'plans/' directory, following the naming convention {date}-{task-name}-{version}.md.

Can I use this for complex code refactoring?

Yes, it is specifically designed to handle long sequences of tasks, ensuring Claude remains focused on completing every step in a refactoring or migration plan.

How does the skill track progress during execution?

The skill updates status indicators in your Markdown file, changing tasks from PENDING [ ] to IN_PROGRESS [~] and finally to DONE [x] or FAILED [!].

Plan Executor

Name: Plan Executor
Author: Activer007

byActiver007

0•

Productivity & Workflow

Executes structured, multi-step task plans with automated progress tracking and persistent status updates.

The Plan Executor skill enables Claude to autonomously navigate complex, multi-stage workflows by following a predefined Markdown plan file. It ensures execution reliability through a formal commitment protocol, sequential task processing, and real-time status tracking within your repository. By reading and updating plan files directly, it provides a transparent audit trail of progress, making it an essential tool for developers managing long-running migrations, refactoring sequences, or deployment checklists that require 100% completion accuracy.

Key Features

01Final verification step to confirm completion of all tasks before exiting

02Automated status tracking using Markdown indicators (PENDING, IN_PROGRESS, DONE, FAILED)

03Real-time file updates to maintain a persistent record of progress

04Formal commitment protocol to ensure all plan items are addressed

050 GitHub stars

06Standardized naming convention for version-controlled task management

Use Cases

01Managing standardized deployment checklists and infrastructure setup tasks

02Automating complex code refactoring sequences across multiple files

03Executing step-by-step database migrations or API version updates

Key Features

01Final verification step to confirm completion of all tasks before exiting

02Automated status tracking using Markdown indicators (PENDING, IN_PROGRESS, DONE, FAILED)

03Real-time file updates to maintain a persistent record of progress

04Formal commitment protocol to ensure all plan items are addressed

050 GitHub stars

06Standardized naming convention for version-controlled task management

Use Cases

01Managing standardized deployment checklists and infrastructure setup tasks

02Automating complex code refactoring sequences across multiple files

03Executing step-by-step database migrations or API version updates