executing-plans

Executes written implementation plans in batches with review checkpoints between batches.

1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/HarmAalbers/claude-requirements-framework --skill executing-plans-harmaalbers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/HarmAalbers/claude-requirements-framework/tree/main/plugins/requirements-framework/skills/executing-plans
Command: npx skills add https://github.com/HarmAalbers/claude-requirements-framework --skill executing-plans-harmaalbers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents uncontrolled, unreviewed implementation by enforcing a structured process for executing a written plan: load the plan, review it critically, execute tasks in small batches, and pause for feedback between batches. ## Core Features & Use Cases - Critical plan review: Reads the plan first and raises questions or concerns with the human partner before writing any code. - Batched execution with checkpoints: Executes a default batch of 3 tasks, marks task progress, runs specified verifications, then reports results and waits for feedback. - Commit and completion workflow: Runs pre-commit review after each batch and hands off to the finishing-a-development-branch skill once all tasks are verified. - Use Case: You have a written implementation plan from a planning session. In a new session, this skill loads the plan, implements the first three tasks with test-driven development, shows verification output, and waits for your review before continuing. ## Quick Start Use the executing-plans skill to implement the plan in docs/plans/feature-x.md, executing tasks in batches and pausing for my review between batches.

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 Claude Code?▼

Load the plan file, review it critically for gaps or concerns, then execute tasks in batches of three with verification after each step. Report results after each batch and wait for feedback before continuing to the next batch.

How many tasks should be executed before pausing for review?▼

The default batch size is three tasks. After completing a batch, show what was implemented along with verification output, then wait for feedback before applying changes or starting the next batch.

What should I do when a plan task is blocked or unclear?▼

Stop executing immediately when you hit a blocker, a failing test, or an unclear instruction. Ask your human partner for clarification rather than guessing, and revisit the plan review step if the approach needs rethinking.

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

No. Never start implementation on main or master without explicit user consent. The recommended setup is an isolated git worktree before beginning execution.

What happens after all plan tasks are complete?▼

After all tasks are verified, run pre-commit review for atomic commits, then use the finishing-a-development-branch skill to verify tests, present merge options, and complete the work.