executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints between batches.
npx skills add a5c-ai/babysitter --skill executing-plans --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- 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`
- Process
- Agents Used
- Tool Use
What does the executing-plans skill do?
Use when you have a written implementation plan to execute in a separate session with review checkpoints between batches.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill executing-plans --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.