executing-plans

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

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/assafmanor/waypoint --skill executing-plans-assafmanor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/assafmanor/waypoint/tree/main/.claude/skills/executing-plans
Command: npx skills add https://github.com/assafmanor/waypoint --skill executing-plans-assafmanor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Written implementation plans often get executed inconsistently: steps get skipped, verifications are ignored, and blockers are worked around with guesses. This Skill enforces a disciplined process for carrying out a plan in a separate session, with critical review up front and explicit checkpoints along the way. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file, identifies questions or concerns, and raises them with the human partner before any code is written. - Structured Task Execution: Converts plan items into todos, marks each in progress, follows bite-sized steps exactly, and runs the specified verifications before marking tasks complete. - Stop-and-Ask Guardrails: Halts execution on blockers, unclear instructions, or repeated verification failures instead of guessing, and never starts implementation on main/master without explicit consent. - Use Case: You have a multi-task implementation plan written in a planning session. Hand it to this Skill in a fresh session and it will create an isolated branch, execute every task with verifications, and finish via the pull-request convention. ## Quick Start Use the executing-plans skill to implement the plan in docs/plans/my-feature-plan.md, reviewing it critically first and stopping if you hit any blockers.

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 workflow. It reviews the plan critically, creates todos for each task, follows the steps exactly, runs the specified verifications, and reports when all tasks are complete.

What should happen before executing a written implementation plan?▼

The plan should be loaded and reviewed critically first, with any questions or concerns raised to the human partner before starting. An isolated branch should also be created or verified so implementation never begins on main or master without explicit consent.

What happens when a plan execution hits a blocker?▼

Execution stops immediately when a blocker appears, such as a missing dependency, failing test, or unclear instruction. The assistant asks for clarification rather than guessing, and returns to the review step if the plan's fundamental approach needs rethinking.

When should I use subagent-driven development instead of executing plans directly?▼

If your platform supports subagents (Claude Code, Codex CLI, Copilot CLI, Gemini CLI), the subagent-driven-development approach is recommended over this skill. This skill is the fallback for sessions without subagent access.

Does executing plans skip verification steps to move faster?▼

No. Each task's verifications must be run as specified in the plan before the task is marked completed. Skipping verifications is explicitly against the workflow, and repeated verification failures trigger a stop-and-ask instead of a workaround.