executing-plans

Execute written plans in reviewable batches with checkpoints and progress reports.

Updated Jul 8, 2022
One-click install
npx skills add https://github.com/limaon/dotfiles --skill executing-plans-limaon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/limaon/dotfiles/tree/main/.config/opencode/skills/executing-plans
Command: npx skills add https://github.com/limaon/dotfiles --skill executing-plans-limaon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executing plans often requires structuring work into reviewable batches to ensure progress visibility and governance.

Core Features & Use Cases

  • Batch-based execution: load a plan, review it critically, and run tasks in controlled batches with checkpoints.
  • Verification and reporting: automatically report outcomes and verification results between batches for stakeholder review.
  • Reuse and continuation: continue with next batches or halt when blockers arise, maintaining traceability.

Quick Start

Load the plan file, review it for concerns, then execute the first batch of tasks (default: 3). For each task: mark as in_progress, perform each step exactly as written, run verifications, and mark as completed. After a batch, present a concise report for feedback and proceed with the next batch or stop if blocked.

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 reviewable batches?

Batch-based plan execution works by grouping project tasks into deterministic sets with explicit checkpoints. You mark tasks as in_progress, perform steps exactly as written, run verifications, and report completion status between batches for stakeholder review.

What is batch-based plan execution with checkpoints?

Batch-based plan execution works by grouping project tasks into deterministic sets with explicit checkpoints. You mark tasks as in_progress, perform steps exactly as written, run verifications, and report completion status between batches for stakeholder review.

How do I maintain progress visibility and governance during multi-step plan execution?

To continue a blocked plan, you halt execution when a blocker arises and maintain traceability through documented completion status. You can reuse the loaded plan file to resume with the next batch or stop entirely based on stakeholder feedback.

Do I need a written plan file to use batch execution with verification?

Batch-based plan execution differs from continuous execution by enforcing deterministic batching with explicit checkpoints and documented completion status. It pauses between batches to present concise verification reports, ensuring stakeholder review before proceeding with the next group of tasks.

How do I continue plan execution when a blocker arises during a batch?

To continue a blocked plan, you halt execution when a blocker arises and maintain traceability through documented completion status. You can reuse the loaded plan file to resume with the next batch or stop entirely based on stakeholder feedback.

What is the best way to structure project tasks for traceability and stakeholder review?

Batch-based plan execution differs from continuous execution by enforcing deterministic batching with explicit checkpoints and documented completion status. It pauses between batches to present concise verification reports, ensuring stakeholder review before proceeding with the next group of tasks.