executing-plans

Executes a written implementation plan with verification checkpoints and blocker handling.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/51hhh/BU03 --skill executing-plans-51hhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/51hhh/BU03/tree/main/.github/skills/executing-plans
Command: npx skills add https://github.com/51hhh/BU03 --skill executing-plans-51hhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn a written implementation plan into completed work by reviewing the plan critically, executing tasks in order, and stopping when a blocker or ambiguity appears.

Core Features & Use Cases

  • Plan Review: Checks the plan for gaps, risks, and unclear instructions before work begins.
  • Stepwise Execution: Tracks each task through in_progress and completed states while following the plan exactly.
  • Checkpointed Delivery: Verifies work as specified, then hands off to the finishing workflow once everything is done.
  • Use Case: Ideal for software changes that need careful coordination, isolated execution, and explicit review points.

Quick Start

Use the executing-plans skill to review this implementation plan, carry out each task with verification checkpoints, and report when the work is complete.

Frequently Asked Questions about executing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute a software implementation plan step by step?

Executing an implementation plan step by step requires reviewing the plan for gaps, tracking task states, verifying work at each checkpoint, and stopping when blockers or ambiguity appear. It requires an isolated worktree for safe execution.

What is the best way to handle blockers when following an implementation plan?

Handling blockers during implementation plan execution means stopping work immediately when ambiguity or risks appear, rather than guessing. The workflow requires explicit task tracking to record where the blocker occurred for later resolution.

Do I need an isolated worktree to carry out a development plan?

An isolated worktree is required to carry out a development plan. It ensures careful coordination by keeping stepwise task execution, verification checkpoints, and blocker handling separate from your main development session.

How does plan review work before starting software development tasks?

Plan review before software development tasks works by checking the written implementation plan for gaps, risks, and unclear instructions. This critical review happens before work begins to prevent execution errors during stepwise task completion.

What happens after completing all tasks in an implementation plan?

After completing all tasks in an implementation plan, the workflow verifies the work as specified and then hands off to a finishing-a-development-branch workflow to finalize the isolated worktree and merge the changes.