Does it support partial plan names?

Yes, you can provide a partial name or ID (e.g., '01'). If multiple plans match the search, the skill will ask for clarification before proceeding.

What happens if a plan's dependencies are not met?

The skill will block execution and report exactly which dependency is missing or not marked as COMPLETED in the PROGRESS.md file, preventing broken implementations.

Can I customize the post-execution behavior?

Yes, through the planner.config.json file, you can enable features like auto-commit (including Conventional Commits support) and automatic CLAUDE.md updates.

How does the skill track progress?

It automatically manages the status of plans in your project's PROGRESS.md file, moving them from NOT STARTED to IN PROGRESS, and finally to COMPLETED or FAILED based on the outcome.

Planner: Plan Executor

Name: Planner: Plan Executor
Author: djalmaaraujo

bydjalmaaraujo

Productivity & Workflow

Executes structured plan files with automated dependency validation, progress tracking, and post-execution workflows.

About

The planner-exec skill automates the implementation phase of a development plan by reading .plan.md files and orchestrating a subagent to perform the actual coding tasks. It ensures project integrity by verifying that prerequisite plans are completed, managing status updates in PROGRESS.md, and optionally handling repetitive tasks like git commits and updating documentation. This skill is essential for developers using a plan-first workflow who want to ensure execution remains consistent, trackable, and safe from dependency conflicts.

Key Features

Automated dependency validation and blocking
Configurable post-execution Git commits
0 GitHub stars
Real-time progress tracking in PROGRESS.md
Conflict detection for in-progress tasks
Automatic CLAUDE.md and documentation updates

Use Cases

Executing a specific feature implementation from a generated plan file
Automating the boilerplate of committing and documenting code changes after task completion
Ensuring complex multi-step migrations are performed in the correct order

About

Key Features

Automated dependency validation and blocking
Configurable post-execution Git commits
0 GitHub stars
Real-time progress tracking in PROGRESS.md
Conflict detection for in-progress tasks
Automatic CLAUDE.md and documentation updates

Use Cases

Executing a specific feature implementation from a generated plan file
Automating the boilerplate of committing and documenting code changes after task completion
Ensuring complex multi-step migrations are performed in the correct order