executing-plans

Execute implementation plans in controlled batches with reviewer checkpoints.

68|6|Updated Apr 16, 2020
One-click install
npx skills add https://github.com/zenobi-us/dotfiles --skill executing-plans-zenobi-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/zenobi-us/dotfiles/tree/main/devtools/files/opencode/skills/executing-plans
Command: npx skills add https://github.com/zenobi-us/dotfiles --skill executing-plans-zenobi-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? Implementing complex plans without structured execution can lead to missed steps, unverified work, and a lack of clear checkpoints for review, increasing the risk of errors and rework.

Core Features & Use Cases

  • Critical Plan Review: Loads and critically reviews implementation plans, identifying questions or concerns before execution.
  • Batch Execution with Checkpoints: Executes tasks in controlled batches (default 3 tasks), reporting for review between each batch.
  • Exact Step Following: Ensures each task is followed precisely, including running specified verifications.
  • Use Case: You've received a detailed plan for a new feature with 15 tasks. Use this Skill to execute the plan in batches of 3, reporting back after each batch for review, ensuring every step is completed and verified correctly.

Quick Start

Use the executing-plans skill to start implementing the first 3 tasks from 'docs/plans/new-feature-plan.md', reporting back after completion.

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 complex implementation plan in controlled batches?

Batch execution breaks large plans into smaller task groups with checkpoints between each batch. Load your plan, execute tasks in batches (default 3), report progress for review, verify completed work, then proceed to the next batch. This ensures structured execution with quality gates and human oversight.

What's the best way to ensure all steps in a development plan are followed correctly?

Critical plan review before execution identifies potential issues upfront. Execute each task exactly as specified, run required verifications immediately after completion, and mark tasks as in_progress and completed. Structured reporting between batches provides checkpoints to catch errors early.

Can I use batch task execution for multi-step feature development?

Yes. Batch execution is designed for scenarios where a complete implementation plan exists and needs phased delivery with reviewer checkpoints. Segment work into manageable batches, report after each batch for human review, and hand off to finishing-a-development-branch when development is complete.

How do I avoid missed steps and rework during plan execution?

Batch execution with verification checkpoints prevents missed steps by marking each task's status and running verifications before marking completion. Structured reporting between batches gives reviewers visibility to catch gaps or issues before proceeding, reducing rework.

What happens after I complete all batches in an implementation plan?

After executing all batches and verifying final tasks, hand off to finishing-a-development-branch to complete branch integration and deployment steps. The Skill focuses on controlled batch execution; downstream branch finishing is a separate workflow step.