Executing Plans
- 587 installs
- 44k repo stars
- Updated July 27, 2026
- sickn33/antigravity-awesome-skills
executing-plans is an agent skill that executes a written implementation plan in bounded batches with verification, human checkpoints, and a forced finish workflow for developers who already have an approved plan to impl
About
executing-plans is a community skill added 2026-02-27 for running written implementation plans in a separate session with architect review checkpoints. The workflow loads the plan file, reviews it critically, raises concerns before starting, executes tasks in batches, and reports between batches for human review. The core principle is batch execution with checkpoints instead of unbounded autonomous runs. The skill announces its use at start and includes a forced finish workflow when all tasks complete. Developers reach for executing-plans when a detailed plan already exists and needs disciplined, verifiable implementation across multiple steps without losing oversight between batches.
- Loads plan, critical review, and TodoWrite before any implementation
- Default batch size of first 3 tasks with in_progress → completed discipline
- Runs plan-specified verifications each task and reports with “Ready for feedback.”
- Iterates batches from human feedback until the plan is complete
- Hard gate: invokes finishing-a-development-branch after all tasks verify
Executing Plans by the numbers
- 587 all-time installs (skills.sh)
- +2 installs in the week ending Jul 20, 2026 (Skillselion tracking)
- Ranked #674 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill executing-plansAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 587 |
|---|---|
| repo stars | ★ 44k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | sickn33/antigravity-awesome-skills ↗ |
How do you execute an implementation plan with review checkpoints?
Run a written implementation plan in bounded batches with verification, human checkpoints, and a forced finish workflow when all tasks are done.
Who is it for?
Developers implementing multi-step written plans who want batched execution with mandatory human review gates between batches.
Skip if: Sessions that still need plan authoring, ad-hoc single-file edits, or fully autonomous runs without human checkpoints.
When should I use this skill?
The user has a written implementation plan and asks to execute it in batches with review between steps.
What you get
Batch-completed plan tasks, inter-batch review reports, resolved concerns log, and a finished implementation summary.
- Batch execution reports
- Completed plan task implementations
- Final finish summary
By the numbers
- Community skill date_added 2026-02-27
Files
Executing 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
1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting 4. If no concerns: Create TodoWrite and proceed
Step 2: Execute Batch
Default: First 3 tasks
For each task: 1. Mark as in_progress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. 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
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Use executing-plans to run an existing plan with checkpoints; use writing-plans when the implementation plan still needs to be authored.
FAQ
When should executing-plans be invoked?
executing-plans fits when a written implementation plan already exists and should run in a separate session. The skill loads the plan, critiques it, batches tasks, and pauses for human review between batches instead of running everything unattended.
What happens before executing-plans starts coding?
executing-plans reads the plan file and reviews it critically first. If concerns appear, executing-plans raises them with the human partner and waits for resolution before beginning batched task implementation.
Is Executing Plans safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.