planner-exec

Execute a plan after validating dependencies and tracking progress via PROGRESS.md.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/djalmaaraujo/claude-code-plugins --skill planner-exec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-exec
Source: https://github.com/djalmaaraujo/claude-code-plugins/tree/main/plugins/planner/skills/planner-exec
Command: npx skills add https://github.com/djalmaaraujo/claude-code-plugins --skill planner-exec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute a single plan workflow with dependency validation, configuration handling, conflict detection, and PROGRESS.md tracking to ensure safe, auditable plan execution.

Core Features & Use Cases

  • Validates dependencies before execution to prevent partial or incorrect runs.
  • Reads planner configuration from plans/planner.config.json to respect auto-commit, CLAUDE.md updates, and re-plan behavior.
  • Detects conflicts with other in-progress plans and blocks execution until safe.
  • Executes the plan by providing the full plan content to a plan-executor subagent and updates PROGRESS.md accordingly.

Quick Start

Request the agent to run a plan file by name (for example, "auth-02-api.plan.md") and let it handle dependency checks, execution, and progress tracking.

Frequently Asked Questions about planner-exec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate dependencies before executing a plan file?

Dependency validation occurs automatically before executing a plan, checking that all prerequisites are completed and detecting conflicts with other in-progress plans to prevent partial or incorrect runs.

What is the best way to track plan execution progress in markdown?

Plan execution progress is tracked via PROGRESS.md, which updates automatically as the plan-executor subagent processes the full plan content and applies configuration rules to ensure auditable execution.

How do I configure auto-commit and re-planning behavior for workflow execution?

Auto-commit, CLAUDE.md updates, and re-planning behavior are configured through the plans/planner.config.json file, which governs how the execution engine applies options during single plan runs.

Can I run a specific plan file by name without manual intervention?

Yes, you can request the agent to run a plan file by name, such as auth-02-api.plan.md, and it will handle dependency checks, conflict detection, execution, and progress tracking automatically.

Why does plan execution block when another plan is in progress?

Plan execution blocks when conflict detection identifies another in-progress plan, ensuring safe execution by preventing concurrent runs from causing conflicts until the environment is clear.

Does single plan execution require external dependencies or components?

Single plan execution has no external dependencies or components, relying entirely on the built-in plan-executor subagent, configuration files, and PROGRESS.md tracking to manage the workflow.