executing-plans

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

Updated Sep 16, 2022
One-click install
npx skills add https://github.com/ryuya-matsunawa/dotfiles --skill executing-plans-ryuya-matsunawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/ryuya-matsunawa/dotfiles/tree/main/agents/.agents/skills/executing-plans
Command: npx skills add https://github.com/ryuya-matsunawa/dotfiles --skill executing-plans-ryuya-matsunawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into working code often fails when steps are skipped, verifications are ignored, or blockers are guessed through. 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 raises questions or concerns with your human partner before any work begins. - Task-by-Task Execution: Marks each task in progress, follows bite-sized steps exactly, runs specified verifications, and marks completion. - Stop-and-Ask Guardrails: Halts immediately on blockers, unclear instructions, or repeated verification failures instead of guessing. - Use Case: You have a multi-task refactoring plan written in a previous session. Hand it to this Skill in a fresh session and it executes every task with checkpoints, then hands off to the finishing-a-development-branch workflow. ## Quick Start Use the executing-plans skill to implement the plan in docs/refactor-plan.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?▼

Provide the written plan file and invoke the executing-plans skill. It reviews the plan critically, creates todos for each task, executes steps exactly as written, runs the specified verifications, and reports when all tasks are complete.

What happens when plan execution hits a blocker?▼

Execution stops immediately when a blocker appears, such as a missing dependency, failing test, or unclear instruction. The skill asks the human partner for clarification rather than guessing or forcing through the problem.

Should I use executing-plans or subagent-driven development?▼

If your platform supports subagents (Claude Code, Codex CLI, Copilot CLI, Gemini CLI), use subagent-driven development instead, as it produces higher quality results. Use executing-plans when subagents are unavailable.

Can executing-plans start work directly on the main branch?▼

No. The skill never starts implementation on main or master without explicit user consent. It integrates with the using-git-worktrees skill to ensure an isolated workspace before executing tasks.

What happens after all plan tasks are completed?▼

After all tasks complete and pass verification, the skill hands off to the finishing-a-development-branch skill, which verifies tests, presents merge or cleanup options, and executes the chosen completion path.