executing-plans

Execute implementation plans in controlled batches with review checkpoints.

Updated Oct 22, 2025
One-click install
npx skills add https://github.com/franroa/chezmoi --skill executing-plans-franroa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/franroa/chezmoi/tree/main/dot_opencode/superpowers/skills/executing-plans
Command: npx skills add https://github.com/franroa/chezmoi --skill executing-plans-franroa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to executing complex implementation plans, breaking them down into manageable batches with critical review checkpoints. It ensures that development proceeds systematically, catching issues early and maintaining alignment with architectural goals.

Core Features & Use Cases

  • Batch Execution: Implements tasks in small, controlled batches (defaulting to 3 tasks), allowing for focused work and frequent review.
  • Critical Review Checkpoints: Requires reporting after each batch for architect feedback, preventing deviations or compounding errors.
  • Blocker Handling: Guides you to stop immediately and ask for help when encountering blockers, rather than guessing or forcing solutions.
  • Use Case: When your human partner provides a detailed implementation plan, use this Skill to execute it. For example, if a plan has 10 tasks, this Skill will guide you to complete the first 3, report for review, then proceed with the next batch.

Quick Start

Announce skill usage

I'm using the executing-plans skill to implement this plan.

The skill will then guide you to load the plan and execute tasks in batches.

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 large implementation plan in manageable stages?

Execute plans in controlled batches with review checkpoints between stages. This approach breaks complex implementation into small task groups (typically 3 tasks per batch), allowing focused work and architect feedback after each batch completes, preventing errors from compounding.

What's the best way to handle code review checkpoints during development?

Implement mandatory review checkpoints after each batch of tasks. Report progress, findings, and blockers after completing each batch, then wait for feedback before proceeding to the next set of tasks. This staged verification catches architectural deviations early.

How do I structure task execution for complex software development workflows?

Orchestrate execution by processing tasks in controlled batches with per-task state tracking and verification between steps. Track progress through each batch, report outcomes, and maintain checkpoint records that enable iterative review and adjustment of the remaining plan.

When should I stop and ask for help during plan execution?

Stop immediately and request guidance when encountering blockers rather than attempting workarounds. The batch-execution approach with mandatory checkpoints ensures blockers surface early, allowing architect feedback before proceeding further into the implementation.

Can I use batch execution for plans with varying task complexity?

Yes. Batch execution works with variable task complexity by tracking state per task and requiring review checkpoints between batches. The flexible batch model accommodates different task sizes while maintaining systematic progress verification and architectural alignment.