executing-plans

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

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/macintorsten/aurapod --skill executing-plans-macintorsten
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/macintorsten/aurapod/tree/main/.github/skills/executing-plans
Command: npx skills add https://github.com/macintorsten/aurapod --skill executing-plans-macintorsten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents uncontrolled, unreviewed execution of implementation plans by enforcing a structured batch-and-checkpoint workflow, so mistakes are caught early instead of after an entire plan is completed. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file and raises questions or concerns with the human partner before any work begins. - Batch Execution with Checkpoints: Executes tasks in batches (default: first 3 tasks), runs specified verifications, then reports results and waits for feedback. - Blocker Handling: Stops immediately on blockers, unclear instructions, or repeated verification failures instead of guessing. - Use Case: You have a written multi-task implementation plan for a new feature. Use this Skill to execute the first three tasks, show verification output, pause for architect review, and continue batch by batch until the plan is complete. ## Quick Start Use the executing-plans skill to implement the plan in my plan file, 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 assistant?▼

Provide the written plan file and invoke the executing-plans skill. It reviews the plan critically, raises concerns before starting, then executes tasks in batches of three with verification, reporting back for feedback between batches.

How many tasks are executed per batch in plan execution?▼

The default batch size is the first three tasks. Each task is marked in_progress, its steps are followed exactly, verifications are run, and it is marked completed before the batch report is presented.

What happens when plan execution hits a blocker?▼

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

Can I change the plan during execution?▼

Yes. When the human partner updates the plan based on feedback, the workflow returns to the review step. The revised plan is re-reviewed critically before execution of the next batch continues.

What happens after all plan tasks are complete?▼

After all tasks are completed 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.