Execute written plans in reviewable batches with checkpoints and progress reports.
npx skills add https://github.com/limaon/dotfiles --skill executing-plans-limaon
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
Executing plans often requires structuring work into reviewable batches to ensure progress visibility and governance.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
tizeeExecute written plans in batches with verification checkpoints and progress reports.
mikeyobrienExecute implementation plans in fixed-size batches with review checkpoints.
pwnk77Create and track development tasks linked to Product Requirement Documents.
bluefishsExecute implementation plan tasks in batches with human review checkpoints.
