executing-plans

Executes written implementation plans task-by-task with verification checkpoints and review gates.

3|Updated Sep 18, 2025
One-click install
npx skills add https://github.com/KingMichaelPark/dotfiles --skill executing-plans-kingmichaelpark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/KingMichaelPark/dotfiles/tree/main/ai/.agents/skills/executing-plans
Command: npx skills add https://github.com/KingMichaelPark/dotfiles --skill executing-plans-kingmichaelpark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into working code often drifts off track: steps get skipped, verifications are ignored, and blockers are guessed around instead of raised. This Skill enforces a disciplined execution loop so plans are followed exactly and issues surface early. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and reviews it for gaps or concerns before any code is written, raising questions with the human partner first. - Task-by-Task Execution: Converts plan items into todos, marks each in progress, follows steps exactly, and runs the specified verifications before marking complete. - Stop-and-Ask Guardrails: Halts execution on blockers, unclear instructions, or repeated verification failures instead of guessing. - Use Case: You have a multi-task implementation plan from a planning session. Hand it to this Skill in a fresh session and it executes every task in order, then hands off to a branch-finishing workflow. ## Quick Start Use the executing-plans skill to implement the plan in docs/plans/feature-auth.md and stop if anything is unclear.

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 with an AI coding assistant?

Load the plan file, review it critically for gaps, then create todos for each task and execute them in order. Run the verifications specified in each step and mark tasks complete only after they pass.

What should an AI do when a plan step fails verification?

Stop executing immediately rather than guessing or forcing through the blocker. Raise the failure with your human partner, whether it is a missing dependency, failing test, or unclear instruction, and wait for clarification.

Can I start implementation directly on the main branch?

No. The workflow requires explicit user consent before starting implementation on main or master, and recommends using an isolated workspace such as a git worktree before executing plan tasks.

When should a plan be sent back for revision instead of executed?

Return to plan review when the plan has critical gaps preventing a start, when your partner updates it based on feedback, or when the fundamental approach needs rethinking. Do not force execution through a broken plan.

What happens after all plan tasks are completed?

After every task is verified and marked complete, the workflow hands off to a finishing-a-development-branch step that verifies tests, presents merge or cleanup options, and executes the chosen action.