KS
Killer-Skills

executing-plans — what is executing-plans what is executing-plans, how to use executing-plans skill, executing-plans batch execution, executing-plans vs manual implementation, executing-plans setup guide, AI agent plan file format, architect review checkpoints, executing-plans implementation best practices

Verified
v1.0.0
GitHub

About this Skill

Perfect for Implementation Agents needing structured batch execution with architectural oversight. executing-plans is an AI agent skill for executing a pre-written implementation plan. Its core principle is batch execution with checkpoints, requiring the agent to load a plan file, review it critically, and report for human partner review between batches.

Features

Loads and reads from a dedicated plan file
Performs a critical review to identify questions or concerns about the plan
Executes implementation tasks in distinct batches
Reports for architect review between each batch of executed tasks
Announces skill usage at the start of a session

# Core Topics

obra obra
[71.9k]
[5546]
Updated: 3/6/2026

Quality Score

Top 5%
61
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add obra/superpowers/executing-plans

Agent Capability Analysis

The executing-plans MCP Server by obra is an open-source Categories.official integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for what is executing-plans, how to use executing-plans skill, executing-plans batch execution.

Ideal Agent Persona

Perfect for Implementation Agents needing structured batch execution with architectural oversight.

Core Value

Enables batch execution of implementation plans with critical review checkpoints, providing plan file loading, task batching, and architect review reporting capabilities.

Capabilities Granted for executing-plans MCP Server

Executing multi-step development plans in batches
Implementing architectural designs with review cycles
Processing complex technical specifications systematically

! Prerequisites & Limits

  • Requires pre-written implementation plan file
  • Needs human architect review between batches
  • Depends on separate session execution context
Project
SKILL.md
2.3 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

Executing Plans

Overview

Load plan, review critically, execute tasks in batches, report for review between batches.

Core principle: Batch execution with checkpoints for architect review.

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

The Process

Step 1: Load and Review Plan

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

Step 2: Execute Batch

Default: First 3 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: Report

When batch complete:

  • Show what was implemented
  • Show verification output
  • Say: "Ready for feedback."

Step 4: Continue

Based on feedback:

  • Apply changes if needed
  • Execute next batch
  • Repeat until complete

Step 5: Complete Development

After all tasks complete and verified:

  • Announce: "I'm using the finishing-a-development-branch skill to complete this work."
  • REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch
  • Follow that skill to verify tests, present options, execute choice

When to Stop and Ask for Help

STOP executing immediately when:

  • Hit a blocker mid-batch (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
  • Between batches: just report and wait
  • Stop when blocked, don't guess
  • Never start implementation on main/master branch without explicit user consent

Integration

Required workflow skills:

  • superpowers:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
  • superpowers:writing-plans - Creates the plan this skill executes
  • superpowers:finishing-a-development-branch - Complete development after all tasks

Related Skills

Looking for an alternative to executing-plans or building a Categories.official AI Agent? Explore these related open-source MCP Servers.

View All

flags

Logo of facebook
facebook

flags is a feature flag management system that enables developers to check flag states, compare channels, and debug feature behavior differences across release channels.

243.6k
0
Design

extract-errors

Logo of facebook
facebook

extract-errors is a skill that assists in extracting and managing error codes in React applications using yarn extract-errors command.

243.6k
0
Design

fix

Logo of facebook
facebook

fix is a technical skill that resolves lint errors, formatting issues, and ensures code quality in declarative, frontend, and UI projects

243.6k
0
Design

flow

Logo of facebook
facebook

Flow is a type checking system for JavaScript, used to validate React code and ensure consistency across applications

243.6k
0
Design