Verified:GitHub

executing-plans

Execute written implementation plans with verification checkpoints and task tracking.

Updated Apr 10, 2026

Search Tags:#plan execution #plan review #git-worktrees #executing-plans #task verification #finishing-branch #subagent guidance

Ready to run

npx skills add https://github.com/LuizEduPP/skills --skill executing-plans-luizedupp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/LuizEduPP/skills/tree/main/executing-plans
Command: npx skills add https://github.com/LuizEduPP/skills --skill executing-plans-luizedupp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the uncertainty and drift that happen when a written implementation plan is executed without a disciplined review, ensuring every task is validated and blockers surfaced before work proceeds.

Core Features & Use Cases

Critical plan review: Load the documented plan, raise questions, and halt until doubts are addressed before touching code.
Structured task execution: Mark tasks as in_progress, follow every step exactly, run specified verifications, and finalize tasks as completed.
Controlled completion: Invoke superpowers:finishing-a-development-branch after successful verification, and integrate superpowers:using-git-worktrees plus superpowers:writing-plans where required.

Quick Start

Follow the executing-plans skill to carry out the provided plan with checkpoints and the required finishing-a-development-branch workflow.

Frequently Asked Questions about executing-plans

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

FAQPage Schema

How do I execute an implementation plan without drift or missing verification steps?▼

Executing an implementation plan without drift requires structured task execution with review checkpoints, marking each task from in_progress to completed only after running specified verifications to surface blockers before proceeding.

What is the best way to review a written development plan before coding?▼

Plan review involves loading the documented task sequence, critically raising questions about the steps, and halting execution until all doubts are addressed before touching any code.

How do I track task status during plan execution to ensure nothing is skipped?▼

Tracking task status during plan execution requires marking each item as in_progress, following every documented step exactly, running verifications, and finalizing tasks as completed upon successful validation.

Can I use git-worktrees when executing plans with review checkpoints?▼

Git-worktrees can be integrated during plan execution to isolate development branches, ensuring structured task tracking and controlled completion workflows remain separate from the main branch.

Does plan execution require a prewritten task sequence to start?▼

Plan execution requires a prewritten task sequence for development or delivery, serving as the foundational document that guides the separate execution session with enforced verification stages.

When should I invoke finishing-a-development-branch during plan execution?▼

Finishing-a-development-branch should be invoked after successful task verification and completion, ensuring all review checkpoints have passed before finalizing the branch integration.