executing-plans

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

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/whatswithavi/Ecchelon_project --skill executing-plans-whatswithavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/whatswithavi/Ecchelon_project/tree/main/.agent/skills/executing-plans
Command: npx skills add https://github.com/whatswithavi/Ecchelon_project --skill executing-plans-whatswithavi

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. This Skill enforces disciplined execution of a pre-written plan in a separate session, with critical review upfront and checkpoints throughout. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and raises questions or concerns with your human partner before writing any code. - Task-by-Task Execution: Works through each bite-sized task, marking progress, following steps exactly, and running the specified verifications. - Stop-and-Ask Discipline: Halts immediately on blockers, unclear instructions, or repeated verification failures instead of guessing. - Use Case: You have a detailed implementation plan from a planning session. Hand it to this Skill in a fresh session, and it reviews the plan, executes every task with verifications, then hands off to a branch-finishing workflow. ## 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?▼

Load the plan file, review it critically and raise concerns before starting, then execute each task in order while running its specified verifications. Mark tasks in progress and completed as you go, and stop to ask for help when blocked instead of guessing.

What should I do before starting to implement a written plan?▼

Read the entire plan and review it critically, identifying questions or gaps. Raise concerns with your human partner first; only proceed once the plan is clear. Set up an isolated workspace such as a git worktree before writing code.

When should plan execution stop and ask for help?▼

Stop immediately when you hit a blocker such as a missing dependency, a failing test, an unclear instruction, or a critical gap in the plan. Ask for clarification rather than guessing, and never force through repeated verification failures.

Does this workflow require subagents to work?▼

No, it works without subagents, but the documentation notes results are significantly better on platforms with subagent support such as Claude Code or Codex. If subagents are available, a subagent-driven development approach is recommended instead.

Can I start implementing a plan directly on the main branch?▼

No. The skill explicitly forbids starting implementation on main or master without explicit user consent. Use an isolated workspace such as a git worktree before beginning any task execution.