executing-plans

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

92|12|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/ARounder-183/HiFiShifter --skill executing-plans-arounder-183
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/ARounder-183/HiFiShifter/tree/main/.github/skills/executing-plans
Command: npx skills add https://github.com/ARounder-183/HiFiShifter --skill executing-plans-arounder-183

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents uncontrolled, unreviewed execution of multi-task implementation plans by enforcing batch execution with human review checkpoints, so mistakes are caught early instead of after an entire plan is applied. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and raises questions or concerns with the human partner before any execution begins. - Batched Task Execution: Executes tasks in batches (default first 3), marking each in-progress and completed, and running the verifications specified in the plan. - Checkpoint Reporting: Reports what was implemented with verification output after each batch, then waits for feedback before continuing. - Use Case: You have a written 12-task refactoring plan. The skill reviews it, executes the first 3 tasks with their verifications, reports results, and pauses for your approval before continuing. ## Quick Start Use the executing-plans skill to implement the plan in docs/refactor-plan.md, executing tasks in batches and reporting back for 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 an AI coding assistant?

Provide the written plan file and invoke the executing-plans workflow. It reviews the plan critically, executes tasks in batches of three by default, runs the specified verifications, and reports back for your feedback between batches.

How many tasks are executed before a review checkpoint?

The default batch size is the first 3 tasks. After each batch completes with its verifications, the skill reports what was implemented and waits for feedback before executing the next batch.

What happens when a task in the plan fails verification?

Execution stops immediately when a blocker is hit, such as a failing test, missing dependency, or unclear instruction. The skill asks for clarification rather than guessing or forcing through the blocker.

Can the plan be changed during execution?

Yes. If the human partner updates the plan based on feedback, the workflow returns to the review step to re-evaluate the revised plan critically before continuing execution.

What happens after all plan tasks are completed?

After all tasks are complete and verified, the workflow hands off to the finishing-a-development-branch sub-skill, which verifies tests, presents completion options, and executes the chosen option.