executing-plans
npx machina-cli add skill guanyang/antigravity-skills/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 SUB-SKILL: Use superpowers: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
- Never start implementation on main/master branch without explicit user consent
Integration
Required workflow skills:
- superpowers:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
- superpowers:writing-plans - Creates the plan this skill executes
- superpowers:finishing-a-development-branch - Complete development after all tasks
Source
git clone https://github.com/guanyang/antigravity-skills/blob/main/skills/executing-plans/SKILL.mdView on GitHub Overview
Executing Plans lets you implement a written plan in a separate session with checkpoints. It loads the plan, reviews it critically, runs tasks in batches with verifications, and reports results between batches for review.
How This Skill Works
Load and critically review the plan; raise concerns with your human partner if needed. Then execute the first batch (default 3 tasks), marking in_progress, following each step, running verifications, and marking completed. After each batch, report what was implemented and the verification outcomes, await feedback, and continue with the next batch until all tasks are complete, then finish via the finishing-a-development-branch sub-skill.
When to Use It
- You have a written implementation plan to execute in a separate session with review checkpoints.
- You need a critical plan review and a defined process before starting.
- You want to execute tasks in batches (default first 3) with built-in verifications.
- You must report implemented work and verification results between batches for partner feedback.
- You are ready to finalize and complete development using finishing-a-development-branch after all tasks are verified.
Quick Start
- Step 1: Load the plan file, read it, and review for questions or concerns.
- Step 2: Start the first batch (default first 3 tasks), execute steps, run verifications, and update status.
- Step 3: Report batch results, receive feedback, and proceed to the next batch or mark completion.
Best Practices
- Critically review the plan first and raise any questions before starting.
- Set up an isolated workspace (git worktrees) as required by integration.
- Follow plan steps exactly and perform all verifications; don’t skip checks.
- Announce at the start that you’re using executing-plans, and report between batches.
- When blocked, stop, don’t guess, and ask for clarification or guidance.
Example Use Cases
- Migrating a database schema exactly as written, executing tasks in batches with checkpoints.
- Implementing a feature according to a specification file with batch-driven testing.
- Running a data-cleaning plan across multiple datasets in scheduled batches.
- Applying a bug-fix plan in stages and verifying each step before proceeding.
- Completing a feature branch by following the plan and finishing with finishing-a-development-branch.
