mindsystem-cc 3.10.1 → 3.11.0

package/mindsystem/workflows/execute-phase.md

@@ -3,7 +3,7 @@ Execute all plans in a phase using wave-based parallel execution. Orchestrator s
 </purpose>
 
 <core_principle>
-The orchestrator's job is coordination, not execution. Each subagent loads the full execute-plan context itself. Orchestrator discovers plans, analyzes dependencies, groups into waves, spawns agents, handles checkpoints, collects results.
+The orchestrator's job is coordination, not execution. Each subagent loads the full execute-plan context itself. Orchestrator discovers plans, analyzes dependencies, groups into waves, spawns agents, collects results.
 </core_principle>
 
 <required_reading>
@@ -68,13 +68,11 @@ ls -1 "$PHASE_DIR"/*-SUMMARY.md 2>/dev/null | sort
 
 For each plan, read frontmatter to extract:
 - `wave: N` - Execution wave (pre-computed)
-- `autonomous: true/false` - Whether plan has checkpoints
 
 Build plan inventory:
 - Plan path
 - Plan ID (e.g., "03-01")
 - Wave number
-- Autonomous flag
 - Completion status (SUMMARY exists = complete)
 
 Skip completed plans. If all complete, report "Phase already executed" and exit.
@@ -87,8 +85,7 @@ Read `wave` from each plan's frontmatter and group by wave number:
 # For each plan, extract wave from frontmatter
 for plan in $PHASE_DIR/*-PLAN.md; do
   wave=$(grep "^wave:" "$plan" | cut -d: -f2 | tr -d ' ')
-  autonomous=$(grep "^autonomous:" "$plan" | cut -d: -f2 | tr -d ' ')
-  echo "$plan:$wave:$autonomous"
+  echo "$plan:$wave"
 done
 ```
 
@@ -113,7 +110,7 @@ Report wave structure with context:
 |------|-------|----------------|
 | 1 | 01-01, 01-02 | {from plan objectives} |
 | 2 | 01-03 | {from plan objectives} |
-| 3 | 01-04 [checkpoint] | {from plan objectives} |
+| 3 | 01-04 | {from plan objectives} |
 
 ```
 
@@ -167,7 +164,6 @@ Execute each wave in sequence. Autonomous plans within a wave run in parallel.
        <execution_context>
        @~/.claude/mindsystem/workflows/execute-plan.md
        @~/.claude/mindsystem/templates/summary.md
-       @~/.claude/mindsystem/references/checkpoints.md
        @~/.claude/mindsystem/references/tdd.md
        </execution_context>
 
@@ -228,93 +224,8 @@ Execute each wave in sequence. Autonomous plans within a wave run in parallel.
    - If continue: proceed to next wave (dependent plans may also fail)
    - If stop: exit with partial completion report
 
-5. **Execute checkpoint plans between waves:**
+5. **Proceed to next wave**
 
-   See `<checkpoint_handling>` for details.
-
-6. **Proceed to next wave**
-
-</step>
-
-<step name="checkpoint_handling">
-Plans with `autonomous: false` require user interaction.
-
-**Detection:** Check `autonomous` field in frontmatter.
-
-**Execution flow for checkpoint plans:**
-
-1. **Spawn agent for checkpoint plan:**
-   ```
-   Task(prompt="{subagent-task-prompt}", subagent_type="general-purpose")
-   ```
-
-2. **Agent runs until checkpoint:**
-   - Executes auto tasks normally
-   - Reaches checkpoint task (e.g., `type="checkpoint:human-verify"`) or auth gate
-   - Agent returns with structured checkpoint (see checkpoint-return.md template)
-
-3. **Agent return includes (structured format):**
-   - Completed Tasks table with commit hashes and files
-   - Current task name and blocker
-   - Checkpoint type and details for user
-   - What's awaited from user
-
-4. **Orchestrator presents checkpoint to user:**
-
-   Extract and display the "Checkpoint Details" and "Awaiting" sections from agent return:
-   ```
-   ## Checkpoint: [Type]
-
-   **Plan:** 03-03 Dashboard Layout
-   **Progress:** 2/3 tasks complete
-
-   [Checkpoint Details section from agent return]
-
-   [Awaiting section from agent return]
-   ```
-
-5. **User responds:**
-   - "approved" / "done" → spawn continuation agent
-   - Description of issues → spawn continuation agent with feedback
-   - Decision selection → spawn continuation agent with choice
-
-6. **Spawn continuation agent (NOT resume):**
-
-   Use the continuation-prompt.md template:
-   ```
-   Task(
-     prompt=filled_continuation_template,
-     subagent_type="general-purpose"
-   )
-   ```
-
-   Fill template with:
-   - `{completed_tasks_table}`: From agent's checkpoint return
-   - `{resume_task_number}`: Current task from checkpoint
-   - `{resume_task_name}`: Current task name from checkpoint
-   - `{user_response}`: What user provided
-   - `{resume_instructions}`: Based on checkpoint type (see continuation-prompt.md)
-
-7. **Continuation agent executes:**
-   - Verifies previous commits exist
-   - Continues from resume point
-   - May hit another checkpoint (repeat from step 4)
-   - Or completes plan
-
-8. **Repeat until plan completes or user stops**
-
-**Why fresh agent instead of resume:**
-Resume relies on Claude Code's internal serialization which breaks with parallel tool calls.
-Fresh agents with explicit state are more reliable and maintain full context.
-
-**Checkpoint in parallel context:**
-If a plan in a parallel wave has a checkpoint:
-- Spawn as normal
-- Agent pauses at checkpoint and returns with structured state
-- Other parallel agents may complete while waiting
-- Present checkpoint to user
-- Spawn continuation agent with user response
-- Wait for all agents to finish before next wave
 </step>
 
 <step name="aggregate_results">
@@ -617,10 +528,6 @@ Each subagent: Fresh 200k context
 - Stop execution
 - Report for manual investigation
 
-**Checkpoint fails to resolve:**
-- User can't approve or provides repeated issues
-- Ask: "Skip this plan?" or "Abort phase execution?"
-- Record partial progress in STATE.md
 </failure_handling>
 
 <resumption>
@@ -637,5 +544,4 @@ If phase execution was interrupted (context limit, user exit, error):
 **STATE.md tracks:**
 - Last completed plan
 - Current wave
-- Any pending checkpoints
 </resumption>