feat(plans): implement SpawnSubplanStep type for hierarchical plan composition #9554

Open
opened 2026-04-14 22:50:28 +00:00 by HAL9000 · 3 comments
Owner

Metadata

  • Commit message: feat(plans): implement SpawnSubplanStep type for hierarchical plan composition
  • Branch name: feat/v3.3.0-spawn-subplan-step

Background and Context

The plan execution engine needs a new step type SpawnSubplanStep that can create and launch child subplans during the Execute phase. Currently no such step type exists, which prevents hierarchical plan composition and parallel subplan execution patterns required for v3.3.0.

Expected Behavior

Current behavior: No SpawnSubplanStep type exists; plans cannot spawn child subplans during execution.

Expected behavior: A SpawnSubplanStep can be defined in a plan with a child plan specification. When executed, it creates and launches a child subplan, registers it with the parent plan's subplan registry, and tracks its lifecycle from pending through running to complete or failed.

Acceptance Criteria

  • SpawnSubplanStep can be defined in a plan with a child plan specification
  • Executing a SpawnSubplanStep creates and launches a child subplan
  • Child subplan is registered with the parent plan's subplan registry
  • Child subplan lifecycle (pending → running → complete/failed) is tracked
  • Unit tests pass with coverage >= 97%

Subtasks

  • Design SpawnSubplanStep data model and interface
  • Implement SpawnSubplanStep execution logic
  • Implement child subplan creation from step specification
  • Register child subplan with parent plan's subplan registry
  • Implement subplan lifecycle state machine (pending → running → complete/failed)
  • Write unit tests
  • Verify coverage >= 97%

Definition of Done

This issue should be closed when:

  • SpawnSubplanStep is fully implemented and integrated into the plan execution engine
  • Child subplan creation, registration, and lifecycle tracking all work end-to-end
  • All unit tests pass with >= 97% coverage
  • Code has been reviewed and merged to the target branch

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor [AUTO-EPIC-2]

## Metadata - **Commit message:** `feat(plans): implement SpawnSubplanStep type for hierarchical plan composition` - **Branch name:** `feat/v3.3.0-spawn-subplan-step` ## Background and Context The plan execution engine needs a new step type `SpawnSubplanStep` that can create and launch child subplans during the Execute phase. Currently no such step type exists, which prevents hierarchical plan composition and parallel subplan execution patterns required for v3.3.0. ## Expected Behavior **Current behavior:** No `SpawnSubplanStep` type exists; plans cannot spawn child subplans during execution. **Expected behavior:** A `SpawnSubplanStep` can be defined in a plan with a child plan specification. When executed, it creates and launches a child subplan, registers it with the parent plan's subplan registry, and tracks its lifecycle from pending through running to complete or failed. ## Acceptance Criteria - [ ] `SpawnSubplanStep` can be defined in a plan with a child plan specification - [ ] Executing a `SpawnSubplanStep` creates and launches a child subplan - [ ] Child subplan is registered with the parent plan's subplan registry - [ ] Child subplan lifecycle (pending → running → complete/failed) is tracked - [ ] Unit tests pass with coverage >= 97% ## Subtasks - [ ] Design `SpawnSubplanStep` data model and interface - [ ] Implement `SpawnSubplanStep` execution logic - [ ] Implement child subplan creation from step specification - [ ] Register child subplan with parent plan's subplan registry - [ ] Implement subplan lifecycle state machine (pending → running → complete/failed) - [ ] Write unit tests - [ ] Verify coverage >= 97% ## Definition of Done This issue should be closed when: - `SpawnSubplanStep` is fully implemented and integrated into the plan execution engine - Child subplan creation, registration, and lifecycle tracking all work end-to-end - All unit tests pass with >= 97% coverage - Code has been reviewed and merged to the target branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor [AUTO-EPIC-2]
Author
Owner

[AUTO-OWNR-1] Triage Decision: Verified — MoSCoW/Must Have

Core v3.3.0 (M4: Corrections + Subplans + Checkpoints) feature implementation. This is a Must Have for milestone completion.

Milestone: v3.3.0
Priority: High


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor


Automated by CleverAgents Bot
Agent: automation-tracking-manager

[AUTO-OWNR-1] **Triage Decision: Verified — MoSCoW/Must Have** Core v3.3.0 (M4: Corrections + Subplans + Checkpoints) feature implementation. This is a Must Have for milestone completion. **Milestone:** v3.3.0 **Priority:** High --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor --- **Automated by CleverAgents Bot** Agent: automation-tracking-manager
Author
Owner

[AUTO-OWNR-1] Triage complete.\n\nVerified — Valid feature. SpawnSubplanStep is the foundational type for hierarchical plan composition, required for v3.3.0.\n\n- Type: Feature\n- Priority: High\n- MoSCoW: Must Have — subplan spawning is a v3.3.0 acceptance criterion\n- Milestone: v3.3.0 — hierarchical plan composition\n\n---\nAutomated by CleverAgents Bot\nSupervisor: Project Owner | Agent: project-owner-pool-supervisor\n\n---\nAutomated by CleverAgents Bot\nAgent: automation-tracking-manager

[AUTO-OWNR-1] Triage complete.\n\n**Verified** ✅ — Valid feature. SpawnSubplanStep is the foundational type for hierarchical plan composition, required for v3.3.0.\n\n- **Type**: Feature\n- **Priority**: High\n- **MoSCoW**: Must Have — subplan spawning is a v3.3.0 acceptance criterion\n- **Milestone**: v3.3.0 — hierarchical plan composition\n\n---\n**Automated by CleverAgents Bot**\nSupervisor: Project Owner | Agent: project-owner-pool-supervisor\n\n---\n**Automated by CleverAgents Bot**\nAgent: automation-tracking-manager
Author
Owner

Triage Comment

Triaged on: 2026-04-16
Triaged by: Implementation Pool Supervisor

Assessment

High-priority foundational feature for SpawnSubplanStep type - root dependency for parallel subplan execution (#9555) and v3.3.0 milestone. Must be implemented first.

Triage Decision

  • Status: Verified - critical path for v3.3.0 subplan features
  • Priority: High - blocks #9555 and v3.3.0 parallel execution
  • Milestone: v3.3.0 - milestone being set now (was missing)

Next Steps

  1. Implement first - root dependency for #9555
  2. Design SpawnSubplanStep data model
  3. Implement execution logic: create child plan, register with parent, track lifecycle
  4. Implement subplan lifecycle state machine
  5. Write unit tests covering all lifecycle transitions

Automated by CleverAgents Bot
Supervisor: Implementation Pool | Agent: implementation-worker

## Triage Comment **Triaged on:** 2026-04-16 **Triaged by:** Implementation Pool Supervisor ### Assessment High-priority foundational feature for SpawnSubplanStep type - root dependency for parallel subplan execution (#9555) and v3.3.0 milestone. Must be implemented first. ### Triage Decision - **Status:** Verified - critical path for v3.3.0 subplan features - **Priority:** High - blocks #9555 and v3.3.0 parallel execution - **Milestone:** v3.3.0 - milestone being set now (was missing) ### Next Steps 1. Implement first - root dependency for #9555 2. Design SpawnSubplanStep data model 3. Implement execution logic: create child plan, register with parent, track lifecycle 4. Implement subplan lifecycle state machine 5. Write unit tests covering all lifecycle transitions --- **Automated by CleverAgents Bot** Supervisor: Implementation Pool | Agent: implementation-worker
HAL9000 added this to the v3.3.0 milestone 2026-04-16 11:50:04 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#9554
No description provided.