execute-phase

MindForge — Execute Phase Command

Usage: /mindforge:execute-phase [N]

Pre-checks (all must pass before execution starts)

1. Read STATE.md — confirm phase [N] is in "planned" status. If STATE.md shows phase [N] as already "complete": ask user to confirm re-execution.

2. Verify plan files exist:

   .planning/phases/[N]/PLAN-[N]-01.md   (minimum one plan required)
   

   If missing: stop. Tell user: "No plans found for Phase [N]. Run /mindforge:plan-phase [N] first."

3. Verify REQUIREMENTS.md exists and has content. If empty: warn user but allow continuation.

4. Run the dependency parser (.mindforge/engine/dependency-parser.md). If validation fails (circular deps, missing deps): stop and report. Do not execute.

Step 1 — Build and display the execution plan

After dependency parsing succeeds, display the wave plan to the user:

Phase [N] Execution Plan
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Wave 1 (parallel)     Wave 2 (parallel)     Wave 3
  ┌─────────────┐       ┌─────────────┐       ┌─────────────┐
  │ Plan 01     │       │ Plan 03     │       │ Plan 05     │
  │ User model  │──┐    │ User API    │──┐    │ Checkout UI │
  └─────────────┘  │    └─────────────┘  │    └─────────────┘
  ┌─────────────┐  │    ┌─────────────┐  │
  │ Plan 02     │──┘    │ Plan 04     │──┘
  │ Product     │       │ Product API │
  └─────────────┘       └─────────────┘

  Total tasks: 5    Waves: 3    Est. time: depends on model speed

Proceed? (yes/no)

If the user says no: stop. Do not execute anything.

Step 2 — Write pre-execution audit entry

Append to .planning/AUDIT.jsonl:

{
  "id": "[uuid-v4]",
  "timestamp": "[ISO-8601]",
  "event": "phase_execution_started",
  "phase": [N],
  "wave_count": [total waves],
  "task_count": [total tasks],
  "agent": "mindforge-orchestrator",
  "session_id": "[session identifier]"
}

Step 3 — Execute waves using the wave executor

Follow the complete protocol in .mindforge/engine/wave-executor.md.