executing-plans

Executes written implementation plans task-by-task with verification checkpoints and review gates.

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill executing-plans-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.codex/plugins/cache/openai-curated/superpowers/dc902811/skills/executing-plans
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill executing-plans-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Written implementation plans often go stale or get executed inconsistently when an AI session improvises instead of following the plan. This Skill enforces disciplined execution of a pre-written plan in a separate session, with critical review up front and verification after every task. ## Core Features & Use Cases - Critical Plan Review: Loads the plan file, identifies questions or gaps, and raises concerns with the human partner before writing any code. - Task-by-Task Execution: Tracks each task with TodoWrite, follows bite-sized steps exactly, and runs the verifications specified in the plan. - Stop-and-Ask Discipline: Halts immediately on blockers, failing verifications, or unclear instructions instead of guessing. - Use Case: You used a planning skill to write a detailed implementation plan for a new API endpoint. In a fresh session, invoke this Skill to execute every task in order, run the specified tests, and hand off to the finishing-a-development-branch workflow when done. ## Quick Start Use the executing-plans skill to implement the plan in docs/plans/add-auth-endpoint.md and stop if anything is unclear.

Frequently Asked Questions about executing-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an implementation plan with an AI coding assistant?▼

Invoke the executing-plans skill with the path to your plan file. It reviews the plan critically, raises concerns before starting, then executes each task in order while running the verifications the plan specifies.

What should an implementation plan contain before executing it?▼

The plan should contain bite-sized tasks with exact steps and explicit verification commands. This skill works best with plans produced by the superpowers:writing-plans skill, which structures tasks for independent execution.

What happens when a plan step fails or is unclear?▼

Execution stops immediately when a blocker, failing verification, or unclear instruction is hit. The skill asks the human partner for clarification rather than guessing or forcing through the problem.

Can I execute a plan on the main or master branch?▼

No. The skill never starts implementation on main or master without explicit user consent. It integrates with superpowers:using-git-worktrees to ensure an isolated workspace before executing tasks.

What happens after all plan tasks are completed?▼

After all tasks complete and pass verification, the skill hands off to superpowers:finishing-a-development-branch, which verifies tests, presents merge or cleanup options, and executes the chosen completion path.

When should I use subagent-driven-development instead of executing plans?▼

Use superpowers:subagent-driven-development when your platform supports subagents, such as Claude Code or Codex. The skill notes that work quality is significantly higher with subagent support than with single-session plan execution.