executing-plans

Coordinate plan execution with task creation, batch work, and review checkpoints.

Updated Aug 27, 2026

Search Tags:#workflow #planning #orchestration #review #task-tracking #batch-processing #execute

Ready to run

npx skills add https://github.com/jacobrocks1212/claude-config --skill executing-plans-jacobrocks1212

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/jacobrocks1212/claude-config/tree/main/user/skills/executing-plans
Command: npx skills add https://github.com/jacobrocks1212/claude-config --skill executing-plans-jacobrocks1212

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the execution of a formal plan by loading task tools, creating tasks, batching work, and requiring reviews between batches, enabling disciplined plan realization in a separate session.

Core Features & Use Cases

Batch execution with architect review checkpoints
Mandatory initialization of task tools and tracking before execution
Plan-driven decision making with human review prompts when concerns arise
Announcement at start to indicate execution mode

Quick Start

Announce the executing-plans workflow, load the mandatory task tools, and begin batch execution following the plan.

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 formal plan with review checkpoints across multiple sessions?▼

Executing a formal plan with review checkpoints involves loading task tools, creating tasks, processing work in batches, and requiring architect reviews between batches to ensure disciplined plan realization across sessions. This approach mandates task initialization before execution proceeds.

What is batch-driven task execution and how does it work for plan orchestration?▼

Batch-driven task execution for plan orchestration groups tasks into sequential batches, executing each batch before pausing for a formal review checkpoint. This mechanism prevents proceeding without tasks and ensures mandatory initialization of task tracking tools before any work begins.

How do I set up task tracking and initialization before starting batch execution?▼

Task tracking setup requires mandatory initialization of task tools immediately after announcing the execution workflow. You must load the tracking components and create tasks from the formal written plan before beginning any batch processing or execution work.

Can I use batch execution with review checkpoints for team agents following a plan?▼

Yes, batch execution with review checkpoints applies to teams or agents that follow a formal plan requiring task creation and formal review between batches. The system prompts human review when concerns arise, ensuring plan-driven decision making throughout the execution process.

Why does plan execution require mandatory task tool initialization before starting?▼

Plan execution requires mandatory task tool initialization to enforce reporting safeguards that prevent proceeding without tasks. This ensures disciplined coordination by loading tracking tools and creating tasks upfront, maintaining structured batch execution and formal review checkpoints.

What are the limitations of batch-driven plan execution with mandatory checkpoints?▼

Batch-driven plan execution with mandatory checkpoints requires a formal written plan to function and cannot proceed without initialized task tools. The review safeguards intentionally halt progress between batches, meaning execution cannot continue until formal review is completed.