Execute Batch Plans

You will now execute the batch plan workflow. Do NOT just report what you'll do - actually execute each step using the tools available.

EXECUTE NOW: Step 1 - Read Configuration

Use the Read tool NOW to read plans/planner.config.json.

Extract these values (use defaults if file not found):

• auto_commit (default: false)
• auto_commit_standard (default: "no_standard")
• auto_update_claude_md (default: false)
• replan_on_exec (default: false)

EXECUTE NOW: Step 2 - Find Plans

Use the Glob tool NOW to find plan files.

Parse the user's arguments to determine the prefix (e.g., "br-doc" from "execute all plans from br-doc").

Run: Glob("plans/{prefix}-*.plan.md") or Glob("plans/{prefix}-*.md")

Store the list of plan files found.

EXECUTE NOW: Step 3 - Spawn Agent

You MUST immediately call the Task tool with these exact parameters:

description: "Batch execute plans"
subagent_type: "planner:plan-batch-orchestrator"
prompt: |
  arguments: [the prefix or comma-separated plan list from Step 2]

  skip_questions: true

  config:
    auto_commit: [value from Step 1]
    auto_commit_standard: [value from Step 1]
    auto_update_claude_md: [value from Step 1]
    replan_on_exec: [value from Step 1]

  BEGIN ORCHESTRATION.

Call the Task tool NOW. Do not delay. Do not just describe what you would do.

Step 4: Report Results

After the Task tool returns, report the execution summary to the user:

════════════════════════════════════════
Batch Execution Complete

Total plans: [X]
Completed: [Y]
Skipped (already done): [Z]
Failed: [W]
Parallel rounds executed: [N]

Execution rounds:
Round 1 (parallel): [plan1], [plan3]
Round 2: [plan2] (waited for plan1)
Round 3: [plan4] (waited for plan2, plan3)

Config actions applied: [list of actions]
════════════════════════════════════════

Reference Information

What This Skill Does

When batch executing plans, this skill:

1. Reads Configuration: From plans/planner.config.json to apply to ALL plans
2. Resolves Plan List: From explicit names or --prefix pattern
3. Spawns Orchestrator: Delegates to plan-batch-orchestrator agent
4. Reports Results: Shows summary of execution rounds and results

Key Features

• Automatic Parallelism: Independent plans run simultaneously for speed
• Sequential Coordination: Waits for dependencies before proceeding
• Smart Ordering: Builds optimal execution rounds from dependency graph
• Resume Capability: Skips already-completed plans
• Failure Handling: Prompts user when dependencies fail

Configuration Options

Configuration is read from plans/planner.config.json (set during planner-setup) and applied to ALL plans:

Note: Configuration is set once during setup and stored in planner.config.json. Users can edit planner.config.json to change settings.

Dependency Graph Building

The plan-batch-orchestrator agent will:

• Read all plan files
• Parse depends_on fields from # Configuration sections
• Build execution rounds
• Check PROGRESS.md for completed plans
• Execute in optimal order with parallelism
• Apply configuration options per plan

Example Execution Flow

User: Execute all auth plans

Step 1: Read configuration
→ From plans/planner.config.json
→ Found: auto_commit: true, auto_update_claude_md: false

Step 2: Resolve plans
→ Found: auth-00-setup.md, auth-01-database.md, auth-02-api.md

Step 3: Spawn batch orchestrator
→ Passes config and plan list

Orchestrator reads plans:
→ Dependencies:
  auth-00-setup.md: (none)
  auth-01-database.md: depends on auth-00-setup.md
  auth-02-api.md: depends on auth-01-database.md

Build rounds:
→ Round 1: auth-00-setup.md
→ Round 2: auth-01-database.md
→ Round 3: auth-02-api.md

Execute:
→ Round 1: auth-00-setup.md completes, auto-commit applied
→ Round 2: auth-01-database.md completes, auto-commit applied
→ Round 3: auth-02-api.md completes, auto-commit applied

Report summary:
→ 3 plans completed, 3 rounds, auto-commit enabled

Benefits