executing-plans

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

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/rub803030/examenprograma --skill executing-plans-rub803030
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/rub803030/examenprograma/tree/main/EXAMEN_PROGRA_2-master/.agents/skills/executing-plans
Command: npx skills add https://github.com/rub803030/examenprograma --skill executing-plans-rub803030

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 your human partner 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 reviews the plan, executes every task with verification, then hands off to the finishing-a-development-branch 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 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 workflow. It reads the plan, reviews it critically for concerns, then executes each task in order using TodoWrite tracking, running the verifications specified in the plan before marking tasks complete.

What should an implementation plan contain before execution?▼

The plan should contain bite-sized tasks with explicit steps and verification commands for each task. Plans created by a dedicated writing-plans workflow pair well, since this skill executes exactly what is written and stops if instructions are unclear or incomplete.

What happens when a plan execution hits a blocker or failing test?▼

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, and returns to plan review if the approach needs rethinking.

Can I run plan execution directly on the main branch?▼

No. The workflow requires an isolated workspace, typically via a git worktree, and never starts implementation on main or master without explicit user consent. Set up the isolated branch before beginning execution.

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

If your platform supports subagents, such as Claude Code or Codex, the subagent-driven-development approach is recommended because it produces higher quality results. Use direct plan execution when subagents are unavailable.