plan-execute

Execute plan-driven code changes from Markdown plan files with verification.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/maxenko/claude-skills --skill plan-execute-maxenko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-execute
Source: https://github.com/maxenko/claude-skills/tree/main/plan-execute
Command: npx skills add https://github.com/maxenko/claude-skills --skill plan-execute-maxenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the safe execution of plan-driven code changes from Markdown plan files.

Core Features & Use Cases

  • Ingests a plan file and any linked sub-files, building a comprehensive worklist.
  • Verifies every target item exists before applying changes and logs discrepancies to ignored.md.
  • Re-verifies previously resolved or ignored items on every run to guard against regressions.

Quick Start

Provide the path to a plan file to begin executing the plan.

Frequently Asked Questions about plan-execute

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

FAQPage Schema
How do I automate executing code changes from a Markdown plan file?

To automate executing code changes from a Markdown plan file, provide the plan file path and the system will recursively ingest linked sub-files to build a comprehensive worklist for safe, automated application.

What happens to ignored items during Markdown plan execution?

Ignored items during Markdown plan execution are logged to ignored.md, and the system re-verifies these previously resolved or ignored items on every subsequent run to guard against regressions.

How does plan-driven code change execution verify target files before applying updates?

Plan-driven code change execution verifies target files by performing existence checks on every target item before applying changes, ensuring file-entity resolution confirms targets exist to prevent discrepancies.

Can I execute recursive Markdown plan documents that link to multiple sub-files?

Yes, you can execute recursive Markdown plan documents by providing the root plan file path, and the system will automatically ingest and resolve all linked sub-files to build a complete worklist.

Why does my plan-driven code change execution log discrepancies to ignored.md?

Plan-driven code change execution logs discrepancies to ignored.md to maintain structured logging of target items that fail existence checks, ensuring verification states are tracked and re-verified against regressions.