Legendary: Plan Lifecycle (Workstream A) #372

Open
opened 2026-02-22 23:41:44 +00:00 by freemo · 1 comment
Owner

Background

This Legendary covers the complete plan lifecycle from domain models through configuration, execution, and apply. It spans M1-M4 milestones and includes plan creation, execution via actors, changeset generation, sandbox merge/apply, correction flows, and subplan support.

Expected Behavior

Users can create plans from actions, execute them via LLM actors, review diffs, apply changes to target resources, correct decisions, and spawn subplans — all through the CLI.

Child Epics

  • #391 Epic: Resource Handlers & Apply Pipeline (CLOSED)
  • #368 Epic: Subplans & Parallelism
  • #825 Epic: ResourceHandler Protocol Completion
  • #8041 Epic: CLI Output Format Compliance — M3 Spec Alignment

Definition of Done

This Legendary is complete when all child Epics and their constituent issues are closed and merged. The plan lifecycle passes all E2E verification suites.


Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Background This Legendary covers the complete plan lifecycle from domain models through configuration, execution, and apply. It spans M1-M4 milestones and includes plan creation, execution via actors, changeset generation, sandbox merge/apply, correction flows, and subplan support. ## Expected Behavior Users can create plans from actions, execute them via LLM actors, review diffs, apply changes to target resources, correct decisions, and spawn subplans — all through the CLI. ## Child Epics - #391 Epic: Resource Handlers & Apply Pipeline (CLOSED) - #368 Epic: Subplans & Parallelism - #825 Epic: ResourceHandler Protocol Completion - #8041 Epic: CLI Output Format Compliance — M3 Spec Alignment ## Definition of Done This Legendary is complete when all child Epics and their constituent issues are closed and merged. The plan lifecycle passes all E2E verification suites. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
freemo self-assigned this 2026-02-24 03:37:59 +00:00
Author
Owner

Day 36 — Epic/Legendary dependency audit findings

This Legendary has 2 missing dependency links that need manual creation via the Forgejo web UI:

  1. #372#368 (Subplans & Parallelism): This Epic is listed in the body as a child of this Legendary but the Forgejo dependency link is missing. #368 is an active, open Epic in v3.4.0.
  2. #372#391 (Resource Handlers & Apply Pipeline): This Epic is listed in the body but has no dependency link to #372. It is closed, but the link should exist for traceability.

Additionally, this Legendary has 2 non-Epic issues (#932, #881) linked as direct children, which breaks the Legendary → Epic → Issue hierarchy convention. These should be children of an appropriate Epic instead:

  • #932 (plan apply --yes bug) should be under Epic #394 (Decision Framework) or a plan lifecycle Epic
  • #881 (rename lifecycle commands) should be under Epic #394 (Decision Framework)

To fix: Open this issue in the web UI → Dependencies section → add #368 and #391 as dependencies (this issue depends on them).

**Day 36 — Epic/Legendary dependency audit findings** This Legendary has **2 missing dependency links** that need manual creation via the Forgejo web UI: 1. **#372 → #368 (Subplans & Parallelism)**: This Epic is listed in the body as a child of this Legendary but the Forgejo dependency link is missing. #368 is an active, open Epic in v3.4.0. 2. **#372 → #391 (Resource Handlers & Apply Pipeline)**: This Epic is listed in the body but has no dependency link to #372. It is closed, but the link should exist for traceability. Additionally, this Legendary has **2 non-Epic issues** (#932, #881) linked as direct children, which breaks the Legendary → Epic → Issue hierarchy convention. These should be children of an appropriate Epic instead: - #932 (plan apply --yes bug) should be under Epic #394 (Decision Framework) or a plan lifecycle Epic - #881 (rename lifecycle commands) should be under Epic #394 (Decision Framework) **To fix:** Open this issue in the web UI → Dependencies section → add #368 and #391 as dependencies (this issue depends on them).
freemo added this to the v3.2.0 milestone 2026-03-17 18:32:47 +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.

Depends on
#364 Epic: Additional CLI Commands & UX
cleveragents/cleveragents-core
#365 Epic: Concurrency & Cleanup
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#372
No description provided.