executing-plans

CRITICAL CONSTRAINTS

You MUST NOT call EnterPlanMode or ExitPlanMode during this skill. This skill operates in normal mode, executing a plan that already exists on disk. Plan mode is unnecessary and dangerous here — it restricts Write/Edit tools needed for implementation.

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 0: Load Persisted Tasks

1. Call TaskList to check for existing native tasks
2. CRITICAL - Locate tasks file: Try <plan-path>.tasks.json, if not found glob for matching .tasks.json
3. If tasks file exists AND native tasks empty: recreate from JSON using TaskCreate, restore blockedBy with TaskUpdate
4. If native tasks exist: verify they match plan, resume from first pending/in_progress
5. If neither: proceed to Step 1b to bootstrap from plan

Update .tasks.json after every task status change.

Step 1: Load and Review Plan

1. Read plan file fully
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: Proceed to task setup

Step 1b: Bootstrap Tasks from Plan (if needed)

If TaskList returned no tasks or tasks don't match plan:

1. Parse the plan document for ## Task N: or ### Task N: headers
2. For each task found, use TaskCreate with:
   • subject: The task title from the plan
   • description: Full task content including steps, files, acceptance criteria
   • activeForm: Present tense action (e.g., "Implementing X")
3. CRITICAL - Dependencies: For EACH task that has blockedBy in the plan or .tasks.json:
   • Call TaskUpdate with taskId and addBlockedBy: [list-of-blocking-task-ids]
   • Do NOT skip this step - dependencies are essential for correct execution order
4. Call TaskList and verify blockedBy relationships show correctly (e.g., "blocked by #1, #2")

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: Use superpowers-extended-cc: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.

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
• Never start implementation on main/master branch without explicit user consent

Integration

Required workflow skills:

• superpowers-extended-cc:using-git-worktrees - REQUIRED: Set up isolated workspace before starting
• superpowers-extended-cc:writing-plans - Creates the plan this skill executes
• superpowers-extended-cc:finishing-a-development-branch - Complete development after all tasks