feat(plan-correction): implement plan correct --mode=append #8534

Open
opened 2026-04-13 20:36:50 +00:00 by HAL9000 · 0 comments
Owner

Metadata

  • Commit message type: feat
  • Scope: plan-correction
  • Branch name prefix: feat/v3.2.0-plan-correct-append

Background and Context

As part of Epic #8481 (Plan Correction Engine), the agents plan correct <id> --mode=append command adds guidance or a correction note to the targeted decision without triggering recomputation. This is useful for annotating decisions without re-running the plan.

This issue depends on the correction data model being implemented first.

This issue blocks Epic #8481.

Expected Behavior

  • agents plan correct <decision-id> --mode=append "<guidance>" adds a correction note to the targeted decision
  • No recomputation is triggered — the plan continues from its current state
  • The correction is persisted as a DecisionCorrection record with type="append"
  • The correction note is visible in agents plan explain <decision-id>

Acceptance Criteria

  • agents plan correct <id> --mode=append "<guidance>" command is registered in the CLI
  • Command adds a correction note without triggering recomputation
  • Correction is persisted as a DecisionCorrection record with type="append"
  • Correction note is visible in agents plan explain output
  • Integration tests verify append correction is persisted and visible
  • Unit tests achieve >= 97% coverage

Subtasks

  • Register plan correct --mode=append in the CLI argument parser
  • Implement append correction service function (no recomputation)
  • Implement correction persistence (create DecisionCorrection record with type="append")
  • Update plan explain to show append corrections in output
  • Write unit tests for append correction
  • Write integration tests for full append correction flow

Definition of Done

  1. plan correct --mode=append command is functional
  2. Integration tests verify correction is persisted and visible in plan explain
  3. Unit tests pass with >= 97% coverage
  4. Code reviewed and merged to main branch

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

## Metadata - **Commit message type**: `feat` - **Scope**: `plan-correction` - **Branch name prefix**: `feat/v3.2.0-plan-correct-append` ## Background and Context As part of Epic #8481 (Plan Correction Engine), the `agents plan correct <id> --mode=append` command adds guidance or a correction note to the targeted decision without triggering recomputation. This is useful for annotating decisions without re-running the plan. This issue depends on the correction data model being implemented first. This issue blocks Epic #8481. ## Expected Behavior - `agents plan correct <decision-id> --mode=append "<guidance>"` adds a correction note to the targeted decision - No recomputation is triggered — the plan continues from its current state - The correction is persisted as a `DecisionCorrection` record with type="append" - The correction note is visible in `agents plan explain <decision-id>` ## Acceptance Criteria - [ ] `agents plan correct <id> --mode=append "<guidance>"` command is registered in the CLI - [ ] Command adds a correction note without triggering recomputation - [ ] Correction is persisted as a `DecisionCorrection` record with type="append" - [ ] Correction note is visible in `agents plan explain` output - [ ] Integration tests verify append correction is persisted and visible - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Register `plan correct --mode=append` in the CLI argument parser - [ ] Implement append correction service function (no recomputation) - [ ] Implement correction persistence (create `DecisionCorrection` record with type="append") - [ ] Update `plan explain` to show append corrections in output - [ ] Write unit tests for append correction - [ ] Write integration tests for full append correction flow ## Definition of Done 1. `plan correct --mode=append` command is functional 2. Integration tests verify correction is persisted and visible in `plan explain` 3. Unit tests pass with >= 97% coverage 4. Code reviewed and merged to main branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.2.0 milestone 2026-04-13 20:44:01 +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#8534
No description provided.