executing-plans

Load, review, and execute plan tasks in batches with verification checkpoints.

8|Updated Sep 7, 2021

Search Tags:#workflow #planning #review #batch #project-management #execute

Ready to run

npx skills add https://github.com/frap129/dotfiles --skill executing-plans-frap129

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordination and execution of plan-driven work requires loading a plan, critically reviewing it, and executing tasks in controlled batches with review checkpoints between batches.

Core Features & Use Cases

Critical plan review before execution: identify questions or blockers and escalate as needed.
Batch-driven task execution: run the first set of tasks in a batch, with per-task status and verifications.
Structured reporting: convey outcomes and verification results to stakeholders between batches.

Quick Start

Load a plan file, review it critically, and execute the first three tasks as a batch with verifications.

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 project plan in controlled batches with review checkpoints?▼

Executing a project plan in controlled batches involves loading the plan, critically reviewing it for blockers, and running tasks in small sets with verification checkpoints and stakeholder reporting between each batch.

What is batch-driven task execution and how does it work for project management?▼

Batch-driven task execution is a workflow mechanism that runs a set of plan tasks sequentially, verifies outcomes per task, and pauses for stakeholder QA review and feedback before proceeding to the next batch.

How do I critically review a project plan before execution to identify blockers?▼

To critically review a project plan before execution, load the plan file and analyze its tasks to identify potential questions, dependencies, or blockers, escalating them to stakeholders before starting batch execution.

Can I use batch execution for collaborative projects where one party provides the plan?▼

Yes, batch execution is designed for collaborative projects where one party provides the plan and the other executes it, utilizing QA reviews, verification checkpoints, and structured reporting between batches to ensure alignment.

How do I report task execution outcomes and verification results to stakeholders?▼

You report task execution outcomes by conveying per-task status and verification results to stakeholders between batches, providing structured feedback that determines whether the next batch of tasks should proceed.

What are the limitations of batch-driven plan execution for complex workflows?▼

The limitation of batch-driven plan execution is that it requires a predefined workflow to load plans, track batch progress, and verify outcomes, meaning continuous execution is paused for mandatory review checkpoints between batches.