executing-plans

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

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Viranya2006/Lumen --skill executing-plans-viranya2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/Viranya2006/Lumen/tree/main/SKILLS/executing-plans
Command: npx skills add https://github.com/Viranya2006/Lumen --skill executing-plans-viranya2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Written implementation plans often go stale or get executed inconsistently when an AI session improvises instead of following the documented steps. This Skill enforces disciplined execution of a pre-written plan in a separate session, with critical review up front and verification after every task. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file, identifies questions or gaps, and raises concerns with the human partner before writing any code. - Task-by-Task Execution: Converts plan items into todos, marks each in progress, follows bite-sized steps exactly, and runs the specified verifications before marking complete. - Controlled Completion and Escalation: Hands off to a finishing-a-development-branch workflow after all tasks pass, and stops to ask for help when blocked rather than guessing. - Use Case: You have a reviewed implementation plan for a new API feature. Start a fresh session, point the AI at the plan file, and it executes every task in an isolated git worktree, runs the tests, and presents merge options when done. ## Quick Start Ask the AI to execute the implementation plan saved in your project using the executing-plans skill, starting in an isolated git worktree.

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?

Save the plan as a file, start a fresh session, and invoke the executing-plans skill. It loads the plan, reviews it critically, creates todos for each task, and executes them one by one with the verifications specified in the plan.

What happens if the plan has gaps or unclear instructions?

The skill stops and raises concerns with the human partner before or during execution. It explicitly avoids guessing when instructions are unclear, a dependency is missing, or a verification fails repeatedly.

Does executing-plans work on the main branch?

No. The skill requires an isolated workspace, typically a git worktree, and never starts implementation on main or master without explicit user consent.

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

Use subagent-driven-development when your platform supports subagents such as Claude Code, Codex CLI, Copilot CLI, or Gemini CLI. The executing-plans skill itself recommends that approach when subagents are available.

What happens after all plan tasks are completed?

The skill invokes the finishing-a-development-branch workflow, which verifies tests, presents completion options, and executes the chosen path to wrap up the development branch.