executing-plans

Execute written implementation plans in ordered batches with review checkpoints.

18|2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/yuanyuekejiJN/AivoClaw --skill executing-plans-yuanyuekejijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/yuanyuekejiJN/AivoClaw/tree/main/extraSkills/executing-plans-0.1.0
Command: npx skills add https://github.com/yuanyuekejiJN/AivoClaw --skill executing-plans-yuanyuekejijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces execution risk when you already have a written plan by ensuring you review it first, run tasks in controlled batches, and produce clear checkpoint reports for architect or partner feedback.

Core Features & Use Cases

  • Plan-first critical review: Reads a provided plan, flags questions or concerns, and asks your human partner before starting when gaps exist.
  • Batch execution with verification: Executes the first N tasks (default first 3), follows the plan’s bite-sized steps precisely, and runs verifications specified in the plan.
  • Checkpoint reporting loop: Reports implemented work and verification output, then waits for feedback before continuing with the next batch.
  • Guardrails for stopping early: Stops immediately when dependencies are missing, tests fail, instructions are unclear, or verification repeatedly fails.
  • Development completion handoff: After all tasks complete and verify, transitions to the required sub-skill superpowers:finishing-a-development-branch for finalization.

Quick Start

Use the executing-plans skill when you have a written implementation plan and want the AI to execute the plan in batches with verification checkpoints and a readiness-for-feedback report 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 a software implementation plan in batches with verification checkpoints?

Batch execution processes tasks in ordered groups, running verifications and pausing for architect feedback before proceeding. This reduces execution risk by validating progress incrementally through checkpoint reporting loops.

What happens during the plan-first critical review before task batching starts?

Plan-first critical review reads the provided implementation plan, flags questions or concerns, and asks your human partner before starting when gaps exist. This strict adherence ensures instructions are clear before batch execution begins.

When should I stop plan execution early due to blockers or verification failures?

Stop plan execution immediately when dependencies are missing, tests fail, instructions are unclear, or verification repeatedly fails. These guardrails prevent compounding errors during batch execution and ensure safe workflow governance.

How do I report task status transitions and verification output between execution batches?

Checkpoint reporting requires reporting implemented work and verification output, then waiting for feedback before continuing with the next batch. Task status transitions from in_progress to completed are tracked throughout this loop.

Can I use batch execution with checkpoint reporting for software delivery workflows requiring incremental validation?

Yes, batch execution with checkpoint reporting applies to software and product implementation scenarios where an architect or human partner must validate progress incrementally. It ensures safe software delivery through controlled task batching.

What is the best way to handle development completion handoff after all plan tasks verify successfully?

Development completion handoff transitions to the required sub-skill for finishing a development branch for finalization. This occurs only after all tasks complete and verify successfully within the batch execution workflow.