mcpField
E
executing-plans

executing-plans

github.com/izyanrajwaniAgent workflows480 installsUpdated 3w ago
Repository

About executing-plans

A skill for carrying out an existing development plan in reviewed batches, with verification and checkpoints for feedback. It directs agents to raise concerns before starting and stop rather than guess when blocked.

Key features

  1. 01Review the plan before execution
  2. 02Execute tasks in small batches
  3. 03Verify each task as specified
  4. 04Report results between batches
  5. 05Stop and ask when blocked

Use cases

  1. 01Implement a reviewed development plan
  2. 02Run work in batches with feedback checkpoints
  3. 03Surface plan gaps before implementation
  4. 04Pause when instructions or verification are unclear

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/izyanrajwani/agent-skills-library --skill executing-plans

After installing, type/executing-plansin Claude Code to confirm it loaded.

Details

From the project README

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

StepActionExit Condition
1Load + ReviewConcerns raised OR TodoWrite created
2Execute Batch3 tasks complete + verified
3ReportShow results, say "Ready for feedback"
4ContinueApply feedback, next batch
5CompleteUse finishing-a-development-branch

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: 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

Comments

Markdown supported