executing-plans

Execute written plans in batches with review checkpoints and result reporting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams implement written plans by executing tasks in batches with review checkpoints and clear handoffs between stages.

Core Features & Use Cases

  • Load plan files, review critically for questions or concerns, and proceed with batch execution
  • Execute tasks in batches with in-progress and completed statuses, including verifications between steps
  • Report results after each batch and continue until the plan is fully implemented, with a final completion phase that triggers finishing-a-development-branch
  • Integration requirements include isolated workspaces via git worktrees and plan-writing and finishing workflows

Quick Start

Load the plan file, review it for concerns, and begin executing the first batch of up to three tasks

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 with structured review checkpoints?

Executing a development plan with review checkpoints involves loading the written plan, critically reviewing it for concerns, and processing tasks in deterministic batches with step verifications before reporting results.

What is the best way to batch tasks during project execution?

Batching tasks during project execution is best handled by processing up to three tasks at a time, verifying steps between batches, and reporting completion statuses before proceeding to the next set.

Does plan execution work with isolated git worktrees?

Plan execution supports integration with isolated workspaces via git worktrees, allowing development, QA, and integration tasks to run deterministically across separate branches before triggering final completion steps.

How do I trigger finishing a development branch after plan execution?

Finishing a development branch triggers automatically during the final completion phase of plan execution, after all batched tasks are fully implemented and reported as complete.

What should I do before starting batch execution of a written plan?

Before starting batch execution, load the plan file and critically review its contents to identify questions, concerns, or integration requirements for the upcoming development and QA tasks.

Can I review a plan critically before processing tasks in batches?

Reviewing a plan critically before processing tasks in batches is a required step to surface concerns, validate integration requirements, and ensure the plan is ready for deterministic execution.