Skill

executing-plans

"Also DO NOT. TRIGGER WHEN: user says 'execute the plan', 'run the plan', 'implement the plan', 'start implementing'. DO NOT TRIGGER WHEN: user wants to write a plan (use writing-plans), wants to brainstorm (use brainstorming), or is doing ad-hoc implementation."

Install

npx claudepluginhub acaprino/alfio-claude-plugins --plugin ai-tooling

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Source: Ported from [obra/superpowers](https://github.com/obra/superpowers) -- `skills/executing-plans`

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

163.7k

ui-demo

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

163.7k

kotlin-patterns

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

163.7k

Stats

Parent Repo Stars0

Parent Repo Forks1

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

Source: Ported from obra/superpowers -- skills/executing-plans

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: This skill works best on platforms with subagent support (such as Claude Code or Codex). When subagents are available, prefer dispatching a fresh subagent per task for higher quality results.

The Process

Step 1: Load and Review Plan

Read plan file
Review critically - identify any questions or concerns about the plan
If concerns: Raise them with your human partner before starting
If no concerns: Create TodoWrite and proceed

Step 2: Execute Tasks

For each task:

Mark as in_progress
Follow each step exactly (plan has bite-sized steps)
Run verifications as specified
Mark as completed

Step 3: Complete Development

After all tasks complete and verified:

Verify all tests pass
Check if the project's CLAUDE.md needs updating based on changes made (new files, changed conventions, updated dependencies)
If CLAUDE.md is stale, propose specific updates before finalizing
Present summary of what was built
Offer options: merge to main, create PR, or clean up branch (squash commits, update docs)

When to Stop and Ask for Help

STOP executing immediately when:

Hit a blocker (missing dependency, test fails, instruction unclear)
Plan has critical gaps preventing starting
You don't understand an instruction
Verification fails repeatedly

Ask for clarification rather than guessing.

When to Revisit Earlier Steps

Return to Review (Step 1) when:

Partner updates the plan based on your feedback
Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Remember

Review plan critically first
Follow plan steps exactly
Don't skip verifications
Reference skills when plan says to
Stop when blocked, don't guess
Never start implementation on main/master branch without explicit user consent

Integration

Related skills and practices:

ai-tooling:writing-plans - Creates the plan this skill executes
Use a git worktree or dedicated branch to isolate work before starting
After completion: verify tests pass, then merge, create PR, or clean up branch