execute-plan

Execute PLAN.md tasks sequentially with human approval and learning persistence.

19|4|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/wunki/amplify --skill execute-plan-wunki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-plan
Source: https://github.com/wunki/amplify/tree/main/skills/execute-plan
Command: npx skills add https://github.com/wunki/amplify --skill execute-plan-wunki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the execution of a PLAN.md file, ensuring tasks are completed one by one with human approval and learning is persisted.

Core Features & Use Cases

  • Task-by-Task Execution: Works through PLAN.md one checked item at a time.
  • Human Oversight: Requires user approval before and after task completion.
  • Learning Persistence: Captures and persists learnings to AGENTS.md or documentation.
  • Plan Mutation Handling: Adapts the plan when requirements change or tasks need splitting.
  • Use Case: After a create-plan skill generates a PLAN.md for adding a new feature, this skill will guide you through implementing each task, asking for confirmation before coding, running tests, and summarizing progress.

Quick Start

Use the execute plan skill to start working on the first task in PLAN.md.

Frequently Asked Questions about execute-plan

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

FAQPage Schema
How do I execute tasks from a PLAN.md file step by step?

To execute tasks from a PLAN.md file, this Skill works through checked items sequentially, managing code implementation, testing, and documentation updates while requiring human approval before and after each task completion.

Can I automate plan execution while maintaining human oversight?

Yes, you can automate plan execution with human oversight by requiring user approval before coding begins and after task completion, ensuring controlled workflow automation for developer productivity.

What is the best way to handle plan mutations during agile development?

Handling plan mutations during agile development involves adapting the PLAN.md file when requirements change or tasks need splitting, ensuring project-wide conventions are updated in AGENTS.md.

How does learning persistence work when implementing a development plan?

Learning persistence when implementing a development work captures project learnings and persists them directly into AGENTS.md or documentation, maintaining project conventions across sequential task execution.

Do I need an existing PLAN.md to start task-by-task execution?

Yes, you need an existing PLAN.md file to start task-by-task execution, as this Skill processes defined tasks sequentially, asking for confirmation before coding and summarizing progress after each item.

Why update AGENTS.md when executing a coding plan?

Updating AGENTS.md when executing a coding plan ensures project-wide conventions reflect any plan mutations or new learnings captured during sequential task implementation, testing, and documentation updates.