Use when you have a written implementation plan to execute in a separate session with review checkpoints between batches.
Scanned 5/29/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill executing-plans --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Executing Plans?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-executing-plans)More formats (shields.io, HTML) on the badges page.
---
name: executing-plans
description: Use when you have a written implementation plan to execute in a separate session with review checkpoints between batches.
---
# 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`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...