obra-executing-plans
Scannednpx machina-cli add skill faulkdev/github-copilot-superpowers/executing-plans --openclawExecuting Plans
Overview
Load plan, review critically, execute tasks in batches, report for review between batches.
Core principle: Batch execution with checkpoints for architect review.
Announce at start: "I'm using the executing-plans skill to implement this plan."
The Process
Step 1: Load and Review Plan
- Read plan file
- Review critically - identify any questions or concerns about the plan
- If concerns: Raise them with your human partner before starting
- If no concerns: Create TodoWrite and proceed
Step 2: Execute Batch
Default: First 3 tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- Mark as completed
Step 3: Report
When batch complete:
- Show what was implemented
- Show verification output
- Say: "Ready for feedback."
Step 4: Continue
Based on feedback:
- Apply changes if needed
- Execute next batch
- Repeat until complete
Step 5: Complete Development
After all tasks complete and verified:
- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
- REQUIRED SKILL: Use
obra-finishing-a-development-branch - Follow that skill to verify tests, present options, execute choice
When to Stop and Ask for Help
STOP executing immediately when:
- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
- Plan has critical gaps preventing starting
- You don't understand an instruction
- Verification fails repeatedly
Ask for clarification rather than guessing.
When to Revisit Earlier Steps
Return to Review (Step 1) when:
- Partner updates the plan based on your feedback
- Fundamental approach needs rethinking
Don't force through blockers - stop and ask.
Remember
- Review plan critically first
- Follow plan steps exactly
- Don't skip verifications
- Reference skills when plan says to
- Between batches: just report and wait
- Stop when blocked, don't guess
Source
git clone https://github.com/faulkdev/github-copilot-superpowers/blob/integrate-obra-superpowers/.github/skills/obra/executing-plans/SKILL.mdView on GitHub Overview
Executing Plans loads your written plan, critiques it for gaps, and then executes tasks in batches with review checkpoints. This approach ensures quality through staged verifications and partner feedback at each milestone.
How This Skill Works
Process: Load and critically review the plan; if concerns arise, raise them before starting; otherwise proceed. Then execute tasks in batches (default first 3), marking in_progress, following plan steps, performing verifications, and marking completion. After each batch, report what was implemented and verification results, then wait for feedback and continue until all tasks are complete; finally invoke finishing-a-development-branch as required.
When to Use It
- You have a written implementation plan and need to execute it in a separate session with review checkpoints.
- You want to run work in batches (default first 3 tasks) with verifications between batches.
- You need to proactively raise concerns or questions about the plan before starting execution.
- You must report batch outcomes and verification results for partner review before continuing.
- You are finishing development and must hand off to obra-finishing-a-development-branch after all tasks are complete.
Quick Start
- Step 1: Announce the use of the executing-plans skill, load the plan, and review critically; raise concerns if any.
- Step 2: Execute the first batch (default first 3 tasks), marking in_progress, following each step, running verifications, and marking completed.
- Step 3: Report batch results (what was implemented and verification outputs), wait for feedback, then continue with the next batch until complete.
Best Practices
- Load and review the plan critically before starting; identify gaps or ambiguities.
- Raise concerns immediately if blockers or missing dependencies are found.
- Execute tasks in small batches (default first 3) with explicit verifications after each batch.
- Reference the plan to guide each task and do not skip verifications or reviews between batches.
- When all tasks are complete, announce completion and transition to the finishing-a-development-branch skill.
Example Use Cases
- Implementing a feature per a documented plan, executed in batches with reviewer sign-off after each batch.
- Refactoring work driven by a written plan, with critical questions raised and addressed before proceeding.
- Bug fix or upgrade plan executed in steps, with per-batch verification outputs shown to stakeholders.
- Major deployment plan carried out in iterative batches, including post-batch reporting and feedback.
- Module upgrade plan finished by invoking the finishing-a-development-branch skill to verify tests and present options.
