executing-plans
Executes development plans in batches, pausing for verification and human feedback between steps.
Install
mkdir -p .claude/skills/executing-plans-alba-intelligence && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19245" && unzip -o skill.zip -d .claude/skills/executing-plans-alba-intelligence && rm skill.zipInstalls to .claude/skills/executing-plans-alba-intelligence
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when you have a written implementation plan to execute in a separate session with review checkpointsKey capabilities
- →Execute tasks in controlled batches
- →Report implemented tasks and verification output for review
- →Stop execution immediately on blockers
- →Complete development using a sub-skill after all tasks are done
How it works
This skill loads an implementation plan, critically reviews it, and executes tasks in small batches. After each batch, it reports the implemented tasks and verification output for review, stopping immediately if any blockers are encountered.
Inputs & outputs
When to use executing-plans
- →Implementing planned features
- →Executing migration steps
- →Running complex refactors
About this skill
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
- 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
When not to use it
- →When guessing instead of asking for clarification
- →When forcing through blockers mid-batch
- →When starting implementation on main/master branch without explicit user consent
Prerequisites
Limitations
- →Requires a written implementation plan
- →Requires verification output between batches
- →Must stop execution immediately when a blocker is hit
How it compares
This skill provides a structured, checkpoint-driven approach to plan execution, ensuring architect review and immediate halting on blockers, unlike simply running through a plan without intermediate checks.
Compared to similar skills
executing-plans side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| executing-plans (this skill) | 0 | 4mo | No flags | Intermediate |
| trello | 41 | 2mo | Review | Beginner |
| executing-plans | 6 | 2mo | No flags | Intermediate |
| github-project-management | 4 | 5mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
executing-plans
obra
Use when you have a written implementation plan to execute in a separate session with review checkpoints
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
project-clickup
incidentfox
ClickUp project management integration for incident tracking and task management
coo-advisor
alirezarezvani
Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.
tlc-spec-driven
tech-leads-club
Project and feature planning with 4 phases - Specify, Design, Tasks, Implement+Validate. Creates atomic tasks with verification criteria and maintains persistent memory across sessions. Stack-agnostic. Use when: (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification, (5) Tracking decisions/blockers across sessions, (6) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "design", "tasks", "implement", "pause work", "resume work".