Use when you have a written implementation plan to execute in a separate session with review checkpoints
Add this skill
npx mdskills install sickn33/executing-plansClear batch execution workflow with checkpoints, but lacks concrete examples of plan format and task structure
1---2name: executing-plans3description: Use when you have a written implementation plan to execute in a separate session with review checkpoints4---56# Executing Plans78## Overview910Load plan, review critically, execute tasks in batches, report for review between batches.1112**Core principle:** Batch execution with checkpoints for architect review.1314**Announce at start:** "I'm using the executing-plans skill to implement this plan."1516## The Process1718### Step 1: Load and Review Plan191. Read plan file202. Review critically - identify any questions or concerns about the plan213. If concerns: Raise them with your human partner before starting224. If no concerns: Create TodoWrite and proceed2324### Step 2: Execute Batch25**Default: First 3 tasks**2627For each task:281. Mark as in_progress292. Follow each step exactly (plan has bite-sized steps)303. Run verifications as specified314. Mark as completed3233### Step 3: Report34When batch complete:35- Show what was implemented36- Show verification output37- Say: "Ready for feedback."3839### Step 4: Continue40Based on feedback:41- Apply changes if needed42- Execute next batch43- Repeat until complete4445### Step 5: Complete Development4647After all tasks complete and verified:48- Announce: "I'm using the finishing-a-development-branch skill to complete this work."49- **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch50- Follow that skill to verify tests, present options, execute choice5152## When to Stop and Ask for Help5354**STOP executing immediately when:**55- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)56- Plan has critical gaps preventing starting57- You don't understand an instruction58- Verification fails repeatedly5960**Ask for clarification rather than guessing.**6162## When to Revisit Earlier Steps6364**Return to Review (Step 1) when:**65- Partner updates the plan based on your feedback66- Fundamental approach needs rethinking6768**Don't force through blockers** - stop and ask.6970## Remember71- Review plan critically first72- Follow plan steps exactly73- Don't skip verifications74- Reference skills when plan says to75- Between batches: just report and wait76- Stop when blocked, don't guess77
Full transparency — inspect the skill content before installing.