miscsubjectsAI governance

Skill · code discipline · MIT

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

The failure this skill exists to stop

Recurring: Concurred plans stalled mid-phase awaiting a go-ahead nobody asked for, instead of executing through every phase.

Source
obra/superpowers ↗
License
MIT — license file travels with the folder
Canonical file
.claude/skills/executing-plans/SKILL.md synced to .agents/skills/executing-plans/SKILL.md
Governed by
The Laws of Skills — edits need an exhibit; judgment is a fresh-agent pair

Executing Plans

Overview

Load plan, review critically, execute all tasks, report when complete.

Announce at start: "I'm using the executing-plans skill to implement this plan."

Note: Tell your human partner that Superpowers works much better with access to subagents (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in ../using-superpowers/references/). If subagents are available, use superpowers:subagent-driven-development instead of this skill.

The Process

Step 1: Load and Review Plan

  1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one
  2. Read plan file
  3. Review critically - identify any questions or concerns about the plan
  4. If concerns: Raise them with your human partner before starting
  5. If no concerns: Create todos for the plan items and proceed

Step 2: Execute Tasks

For each task:

  1. Mark as in_progress
  2. Follow each step exactly (plan has bite-sized steps)
  3. Run verifications as specified
  4. Mark as completed

Step 3: Complete Development

After all tasks complete and verified:

When to Stop and Ask for Help

STOP executing immediately when:

Ask for clarification rather than guessing.

When to Revisit Earlier Steps

Return to Review (Step 1) when:

Don't force through blockers - stop and ask.

Remember

Folder contents · 2 files