obra-executing-plans
Scannednpx machina-cli add skill faulkdev/github-copilot-superpowers/obra-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)
- Code navigation: When locating code sections, use Serena MCP
find_symbolandget_symbols_overviewfor fast, surgical navigation - Code editing: Use Serena MCP symbol editing tools (
insert_before_symbol,insert_after_symbol,replace_symbol_body) for precise modifications - See
serena-mcp-integration-guide.mdfor detailed tool usage
- Code navigation: When locating code sections, use Serena MCP
- 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/obra-executing-plans/SKILL.mdView on GitHub Overview
The Executing Plans skill loads a written plan, reviews it critically, and executes tasks in batches with review checkpoints between batches. It emphasizes batch execution with architect review and requires an announcement at the start. This approach helps ensure alignment, detect issues early, and manage risk.
How This Skill Works
Load and review the plan critically; raise concerns if needed. Execute batches with the first three tasks by marking in_progress, making exact changes using Serena MCP tools, and running verifications. After each batch, report results and wait for feedback before continuing.
When to Use It
- When you have a written implementation plan to execute in a separate session with review checkpoints.
- When critical gaps or questions arise, requiring you to raise concerns before starting.
- When you need architect review at batch boundaries to approve progress before proceeding.
- When you want to minimize risk by processing work in small, verifiable batches.
- When completing tasks toward a development branch and then using the finishing-a-development-branch workflow after verification.
Quick Start
- Step 1: Load and critically review the plan; raise any questions or concerns.
- Step 2: Execute the first 3 tasks, navigating code with Serena MCP tools and applying edits exactly as specified; run verifications.
- Step 3: Report what was implemented and verification outputs, then await feedback before proceeding.
Best Practices
- Read and critique the entire plan before starting any work.
- Raise concerns immediately if anything is unclear or risky.
- Follow the plan steps exactly; avoid improvisation unless explicitly allowed.
- Use the designated Serena MCP navigation and editing tools for precise changes.
- Run verifications between batches and pause for feedback before continuing.
Example Use Cases
- Implementing a new feature exactly as documented in a plan, in a fresh branch, with batch-by-batch execution.
- Breaking a complex refactor into three-task batches, each verified before moving to the next.
- Submitting batch verification results to the architect and awaiting feedback before continuing.
- Stopping immediately when blockers or missing dependencies are encountered and seeking clarification.
- Completing all tasks and then using finishing-a-development-branch to verify tests and present options.
