executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints between batches.
Best use case
executing-plans is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when you have a written implementation plan to execute in a separate session with review checkpoints between batches.
Teams using executing-plans should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/executing-plans/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How executing-plans Compares
| Feature / Agent | executing-plans | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when you have a written implementation plan to execute in a separate session with review checkpoints between batches.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Executing Plans ## Overview Load plan, review critically, execute tasks in batches, report for human review between batches. Supports resume via `.tasks.json` persistence. **Core principle:** Batch execution with checkpoints for architect review. ## When to Use - You have a written implementation plan on disk - Executing in a separate/parallel session - Want human checkpoints between task batches ## Process 1. Load persisted tasks (resume support) 2. Verify/setup worktree 3. Execute tasks in batches (default 3) 4. Report after each batch, wait for feedback 5. Finish branch after all tasks complete ## Agents Used - Process agents defined in `executing-plans.js` - References `using-git-worktrees` for workspace isolation - References `finishing-a-development-branch` for completion ## Tool Use Invoke via babysitter process: `methodologies/superpowers/executing-plans`
Related Skills
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code. Creates bite-sized TDD implementation plans with dependency tracking.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.