Executing Plans (OpenSpec Integration)

Overview

Load plan from OpenSpec change directory, 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 openspec-executing-plans to implement this plan."

The Process

Step 1: Load and Review Plan

Read from OpenSpec (instead of docs/plans/):

# Find the active change
openspec list --json

# Read the plan
cat openspec/changes/<name>/plan.md

# Also read specs for reference
ls openspec/changes/<name>/specs/

Review critically — identify any questions or concerns about the plan.

• If concerns: Raise them with your human partner before starting
• 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:

• Announce: "I'm using openspec-finishing-branch to complete this work."
• REQUIRED SUB-SKILL: Use openspec-finishing-branch
• Follow that skill to verify tests, present options, execute choice, archive

When to Stop and Ask for Help

STOP executing immediately when:

• Hit a blocker mid-batch
• Plan has critical gaps
• You don't understand an instruction
• Verification fails repeatedly

Ask for clarification rather than guessing.

Remember

• Review plan critically first
• Follow plan steps exactly
• Don't skip verifications
• Between batches: just report and wait
• Stop when blocked, don't guess