ai-proj-helper/plugins/executing-plans-plugin/skills/SKILL.md

name, description

name	description
executing-plans	Use when you have a written implementation plan to execute in a separate session with review checkpoints

Executing Plans

Overview

Load plan, review critically, create branch, 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: Proceed to branch setup

Step 2: Setup Branch

Before any implementation, ensure proper branch isolation.

1. Check if already on a feature branch for this task
2. If not, use /pr start to create one:

   /pr start <type> <REQ-id> <name>
   # Example: /pr start feature REQ-123 user-login
   

3. If no REQ-id available, ask user or create branch manually:

   git fetch origin
   git checkout -b <type>/<descriptive-name> origin/main
   

4. Confirm branch is ready before proceeding

Branch types: feature, fix, refactor

Step 3: Create Tasks and Execute Batch

Default: First 3 tasks

1. Create TodoWrite tasks from plan
2. For each task in batch:
   • Mark as in_progress
   • Follow each step exactly (plan has bite-sized steps)
   • Run verifications as specified
   • Mark as completed

Step 4: Report

When batch complete:

• Show what was implemented
• Show verification output
• Say: "Ready for feedback."

Step 5: Continue

Based on feedback:

• Apply changes if needed
• Execute next batch
• Repeat until complete

Step 6: 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: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
• Create feature branch before implementation
• 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