sp-executing-plans

name	sp-executing-plans
description	Batch plan execution with human review checkpoints — use when you have a written implementation plan to execute. Loads the plan, reviews it critically, executes tasks in batches of 3, and reports for review between batches.
tags	["execution","planning","workflow","batch","implementation"]
version	1.0.0
risk	guarded
triggers	["execute the plan","implement the plan","run the plan","start executing","carry out the plan","execute tasks","proceed with implementation"]
requirements	{"cli":[],"env":[]}
upstream_ref	skills/executing-plans/SKILL.md
author	AlphaComposite
license	MIT
dependencies	["sp-writing-plans","sp-using-git-worktrees","sp-finishing-a-development-branch"]

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 sp-executing-plans skill to implement this plan."

Dependency notes:

• This skill requires sp-using-git-worktrees (not yet ported) to set up an isolated workspace before starting. Until ported, use the upstream using-git-worktrees skill or set up a git worktree manually.
• This skill requires sp-finishing-a-development-branch (not yet ported) to complete development after all tasks. Until ported, use the upstream finishing-a-development-branch skill or perform branch completion steps manually.

The Process

Step 1: Load and Review Plan

1. Read the 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 a task list and proceed

Step 2: Execute Batch

Default: First 3 tasks

For each task:

1. Mark as in_progress
2. Follow each step exactly (the plan has bite-sized steps)
3. Run verifications as specified
4. Mark as completed

Step 3: Report

When batch is 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 are complete and verified:

• Announce: "I'm using the sp-finishing-a-development-branch skill to complete this work."
• REQUIRED SUB-SKILL: Use sp-finishing-a-development-branch (or upstream finishing-a-development-branch if not yet ported)
• 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 the 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:

• sp-using-git-worktrees — REQUIRED: Set up isolated workspace before starting (not yet ported; use upstream using-git-worktrees in the interim)
• sp-writing-plans — Creates the plan this skill executes (not yet ported; use upstream writing-plans in the interim)
• sp-finishing-a-development-branch — Complete development after all tasks (not yet ported; use upstream finishing-a-development-branch in the interim)