executing-plans

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

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SleyiW/iWana-neXt --skill executing-plans-sleyiw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/SleyiW/iWana-neXt/tree/main/.agents/skills/executing-plans
Command: npx skills add https://github.com/SleyiW/iWana-neXt --skill executing-plans-sleyiw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into working code often goes wrong 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 failures surface early. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and raises questions or concerns with you before any code is written. - Task-by-Task Execution: Tracks each task with TodoWrite, follows bite-sized steps exactly, and runs the verifications specified in the plan. - Stop-and-Ask Discipline: Halts immediately 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, verifies each one, and finishes the development branch when done. ## Quick Start Execute the implementation plan in plan.md, reviewing it critically first and stopping to ask me if anything is unclear or blocked.

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 assistant?

Provide the written plan file and instruct the assistant to execute it. The plan is reviewed critically first, then each task is marked in progress, followed exactly, verified as specified, and marked complete before moving on.

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 assistant asks for clarification rather than guessing, and resumes only after the issue is resolved.

Should I use subagents for plan execution?

Yes, if your platform supports subagents, the subagent-driven-development workflow is recommended over this skill because it produces higher quality results. This skill is the fallback for sessions without subagent support.

Can plan execution start directly on the main branch?

No. Implementation never starts on the main or master branch without explicit user consent. Work happens on a development branch, which is finished through the finishing-a-development-branch workflow after all tasks pass verification.

What are the limitations of executing plans without review?

Skipping the critical review step risks executing a plan with gaps or flawed assumptions. Concerns must be raised with your human partner before starting, and fundamental approach problems require returning to the review step.