🎯

executing-plans

🎯Skill

from izyanrajwani/agent-skills-library

What it does

Systematically executes implementation plans by loading, critically reviewing, executing tasks in batches, and reporting progress for architect feedback.

📦

Part of

izyanrajwani/agent-skills-library(10 items)

executing-plans

Installation

📋 No install commands found in docs. Showing default command. Check GitHub for actual instructions.

Quick InstallInstall with npx

npx skills add izyanrajwani/agent-skills-library --skill executing-plans

Need more details? View full documentation on GitHub →

3Installs

AddedFeb 4, 2026

View on GitHub Back to Skills

Skill Details

SKILL.md

Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.

Overview

# 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."

Quick Reference

| Step | Action | Exit Condition |

|------|--------|----------------|

| 1 | Load + Review | Concerns raised OR TodoWrite created |

| 2 | Execute Batch | 3 tasks complete + verified |

| 3 | Report | Show results, say "Ready for feedback" |

| 4 | Continue | Apply feedback, next batch |

| 5 | Complete | Use finishing-a-development-branch |

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 Batch

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

Common Mistakes

Executing without critical review

Problem: Blindly following plan with gaps
Fix: Step 1 explicitly requires raising concerns first

Batch size drift

Problem: Doing 5-10 tasks without checkpoint
Fix: Default is 3. Report after EVERY batch.

Guessing through blockers

Problem: Making assumptions when stuck
Fix: STOP immediately, ask for clarification

Skipping verification commands

Problem: Mark complete without running tests
Fix: Each task has verification - run it

Integration

Called by:

writing-plans (Parallel Session choice)

Calls:

finishing-a-development-branch (Step 5)

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

More from this repository9

🎯

systematic-debugging🎯Skill

Systematically investigates root causes of bugs by tracing data flow, analyzing system components, and forming precise hypotheses before attempting fixes.

🎯

verification-before-completion🎯Skill

Enforces evidence-first verification by requiring concrete proof via specific commands before claiming task completion or success.

🎯

using-git-worktrees🎯Skill

Creates isolated Git workspaces for parallel development without disrupting the current working tree.

🎯

test-driven-development🎯Skill

Guides developers through writing tests first, implementing minimal code to pass, and refactoring while ensuring verified test coverage for behavior changes.

🎯

finishing-a-development-branch🎯Skill

Streamlines Git branch completion by running tests, determining merge target, and guiding developers through merging or creating pull requests.

🎯

requesting-code-review🎯Skill

Requests a comprehensive code review by dispatching a subagent to analyze code changes, identify potential issues, and provide structured feedback before merge.

🎯

brainstorming🎯Skill

Collaboratively explores and refines ideas into validated design specifications through iterative, focused questioning and incremental validation.

🎯

dispatching-parallel-agents🎯Skill

Dispatches independent test failures or bug domains to specialized subagents for concurrent, focused investigation and resolution.

🎯

writing-plans🎯Skill

Generates comprehensive, test-driven implementation plans with precise file paths, code snippets, and verification steps for multi-step development tasks.