executing-plans

Execute written implementation plans in batches with review checkpoints.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/NAinfini/Guild_Management --skill executing-plans-nainfini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/NAinfini/Guild_Management/tree/main/.kilocode/skills/executing-plans
Command: npx skills add https://github.com/NAinfini/Guild_Management --skill executing-plans-nainfini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables you to implement a written plan by executing work in defined batches with review checkpoints, reducing drift and ensuring oversight.

Core Features & Use Cases

  • Batch-driven execution: process tasks in fixed groups with explicit verifications.
  • Critical-review integration: raise questions or concerns before proceeding and pause when blockers occur.
  • Seamless completion: report outcomes after each batch and continue until the plan is fully implemented.

Quick Start

Load the plan file, review it critically, execute the first batch of three tasks, verify outcomes, and report results for review.

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 development plan in batches with verification checkpoints?

Executing a development plan in batches involves processing tasks in fixed groups, enforcing critical review at each checkpoint, verifying outcomes, and reporting results before proceeding to the next batch.

What is the best way to prevent drift when implementing a written software plan?

Preventing drift during plan implementation requires batch-driven execution with explicit verifications, raising concerns before proceeding, and pausing when blockers occur to ensure continuous oversight.

How do I set up an isolated workspace for batch plan execution?

Setting up an isolated workspace for batch plan execution requires using git worktrees to manage development branches, ensuring changes remain separated until verification is complete.

Can I pause execution if a critical review identifies a blocker in the plan?

Yes, critical-review integration pauses execution when blockers occur or concerns are identified, requiring explicit verification and reporting of outcomes before continuing to the next batch.

Do I need a written plan file before starting batch execution?

Yes, batch execution requires a pre-written plan file with clear steps to load, review critically, and process in groups of tasks with verifications until fully implemented.

How does post-completion verification work for a development branch?

Post-completion verification for a development branch involves reporting outcomes after the final batch, confirming all plan steps are implemented, and ensuring the isolated workspace passes review.