mcpField
E
executing-plans

executing-plans

github.com/pedronauckAgent workflows647251 installsUpdated 2w ago
Repository

About executing-plans

A skill for coding agents that guides implementation from a written plan in reviewed batches. It emphasizes critical plan review, verification, progress reports, and stopping to ask when blocked.

Key features

  1. 01Review plans before execution
  2. 02Execute tasks in small batches
  3. 03Run specified verifications
  4. 04Report between batches
  5. 05Stop and seek clarification when blocked

Use cases

  1. 01Implementing a reviewed development plan
  2. 02Checking task results before proceeding
  3. 03Raising plan gaps before coding
  4. 04Handling failed verification or unclear steps

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pedronauck/skills --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."

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:

  • Verify all tests pass and build succeeds
  • Present completion summary to your human partner
  • Execute final steps based on their feedback

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

Comments

Markdown supported