cleveragents/cleveragents-core

Fork 3

UAT: `agents plan use` output uses generic plan details panel instead of spec-required multi-panel output (Plan Created, Inputs, Actors, Automation, Context, Next Steps) #4128

New issue

Open

opened 2026-04-06 10:30:44 +00:00 by freemo · 2 comments

freemo commented

2026-04-06 10:30:44 +00:00

Owner

Metadata

Branch: fix/cli/plan-use-output-panels
Commit Message: fix(cli): add spec-required multi-panel output to agents plan use command
Milestone: None (backlog)
Parent Epic: #3374

Summary

The agents plan use command uses a generic _print_lifecycle_plan() helper that shows a single plan details panel. The specification requires six distinct panels: Plan Created, Inputs, Actors, Automation, Context, and Next Steps.

What Was Tested

Reviewed src/cleveragents/cli/commands/plan.py, the use_action() function (line 1526) and _print_lifecycle_plan() helper (line 1326), and compared against the specification's Example 1 workflow (spec lines 36447–36501).

Expected Behavior (from spec)

The spec (lines 36447–36501) requires six panels:

╭─ Plan Created ──────────────────────────╮
│ Plan ID: 01HXR1C1D2E3F4G5H6I7J8K9L0     │
│ Phase: strategize                       │
│ Action: local/fix-bug                   │
│ Project: local/api-service              │
│ Automation: manual                      │
│ Attempt: 1                              │
╰─────────────────────────────────────────╯

╭─ Inputs ──────────────────────────────────────────────────────────────╮
│ - bug_description="The /health endpoint returns HTTP 500..."          │
│ - affected_file="src/routes/health.py"                                │
│ - automation_profile=manual                                           │
╰───────────────────────────────────────────────────────────────────────╯

╭─ Actors ──────────────────────────────────────╮
│ Strategy: anthropic/claude-3.5-sonnet         │
│ Execution: anthropic/claude-3.5-sonnet        │
│ Estimation: (none)                            │
╰───────────────────────────────────────────────╯

╭─ Automation ──────────────────────────╮
│ Profile: manual                       │
│ Source: plan override                 │
│ Read-Only: no                         │
╰───────────────────────────────────────╯

╭─ Context ─────────────────────────╮
│ Resources: 1 (git-checkout)       │
│ Indexed Files: 41                 │
│ View: strategize                  │
│ Hot Token Budget: 8,000           │
╰───────────────────────────────────╯

╭─ Next Steps ───────────────────────────────────────╮
│ - agents plan execute 01HXR1C1D2E3F4G5H6I7J8K9L0   │
│ - agents plan status 01HXR1C1D2E3F4G5H6I7J8K9L0    │
│ - agents plan tree 01HXR1C1D2E3F4G5H6I7J8K9L0      │
╰────────────────────────────────────────────────────╯

✓ OK Plan created

Actual Behavior

The code at src/cleveragents/cli/commands/plan.py lines 1708–1719 calls _print_lifecycle_plan(plan, title="Plan Created") which outputs a single generic panel with all plan details merged together, not the six distinct panels required by the spec.

Code Location

File: src/cleveragents/cli/commands/plan.py
Function: use_action() at line 1526
Output section: lines 1705–1719

Steps to Reproduce

Create an action: agents action create --config ./actions/fix-bug.yaml
Create a plan: agents plan use local/fix-bug local/api-service --arg bug_description="..."
Observe the output — a single generic panel is printed instead of six distinct panels

Impact on Workflow Examples

This blocks visual verification of all 18 workflow examples in the spec that use agents plan use. The command functions correctly (plan is created), but the output does not match the spec.

Subtasks

Replace _print_lifecycle_plan() call with dedicated _print_plan_created_output() function
Plan Created panel: Plan ID, Phase, Action, Project, Automation, Attempt
Inputs panel: list all plan arguments and automation_profile
Actors panel: Strategy, Execution, Estimation actors
Automation panel: Profile name, Source (plan override/action/global), Read-Only flag
Context panel: Resources count/types, Indexed Files, View, Hot Token Budget
Next Steps panel: execute, status, tree commands with plan ID
Add ✓ OK Plan created confirmation line

Definition of Done

agents plan use <action> <project> outputs six panels matching the spec format
All panels show correct data from the created plan
All nox stages pass
Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone None (backlog). It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-new-issue-creator

## Metadata - **Branch**: `fix/cli/plan-use-output-panels` - **Commit Message**: `fix(cli): add spec-required multi-panel output to agents plan use command` - **Milestone**: None (backlog) - **Parent Epic**: #3374 ## Summary The `agents plan use` command uses a generic `_print_lifecycle_plan()` helper that shows a single plan details panel. The specification requires six distinct panels: Plan Created, Inputs, Actors, Automation, Context, and Next Steps. ## What Was Tested Reviewed `src/cleveragents/cli/commands/plan.py`, the `use_action()` function (line 1526) and `_print_lifecycle_plan()` helper (line 1326), and compared against the specification's Example 1 workflow (spec lines 36447–36501). ## Expected Behavior (from spec) The spec (lines 36447–36501) requires six panels: ``` ╭─ Plan Created ──────────────────────────╮ │ Plan ID: 01HXR1C1D2E3F4G5H6I7J8K9L0 │ │ Phase: strategize │ │ Action: local/fix-bug │ │ Project: local/api-service │ │ Automation: manual │ │ Attempt: 1 │ ╰─────────────────────────────────────────╯ ╭─ Inputs ──────────────────────────────────────────────────────────────╮ │ - bug_description="The /health endpoint returns HTTP 500..." │ │ - affected_file="src/routes/health.py" │ │ - automation_profile=manual │ ╰───────────────────────────────────────────────────────────────────────╯ ╭─ Actors ──────────────────────────────────────╮ │ Strategy: anthropic/claude-3.5-sonnet │ │ Execution: anthropic/claude-3.5-sonnet │ │ Estimation: (none) │ ╰───────────────────────────────────────────────╯ ╭─ Automation ──────────────────────────╮ │ Profile: manual │ │ Source: plan override │ │ Read-Only: no │ ╰───────────────────────────────────────╯ ╭─ Context ─────────────────────────╮ │ Resources: 1 (git-checkout) │ │ Indexed Files: 41 │ │ View: strategize │ │ Hot Token Budget: 8,000 │ ╰───────────────────────────────────╯ ╭─ Next Steps ───────────────────────────────────────╮ │ - agents plan execute 01HXR1C1D2E3F4G5H6I7J8K9L0 │ │ - agents plan status 01HXR1C1D2E3F4G5H6I7J8K9L0 │ │ - agents plan tree 01HXR1C1D2E3F4G5H6I7J8K9L0 │ ╰────────────────────────────────────────────────────╯ ✓ OK Plan created ``` ## Actual Behavior The code at `src/cleveragents/cli/commands/plan.py` lines 1708–1719 calls `_print_lifecycle_plan(plan, title="Plan Created")` which outputs a single generic panel with all plan details merged together, not the six distinct panels required by the spec. ## Code Location - File: `src/cleveragents/cli/commands/plan.py` - Function: `use_action()` at line 1526 - Output section: lines 1705–1719 ## Steps to Reproduce 1. Create an action: `agents action create --config ./actions/fix-bug.yaml` 2. Create a plan: `agents plan use local/fix-bug local/api-service --arg bug_description="..."` 3. Observe the output — a single generic panel is printed instead of six distinct panels ## Impact on Workflow Examples This blocks visual verification of all 18 workflow examples in the spec that use `agents plan use`. The command functions correctly (plan is created), but the output does not match the spec. ## Subtasks - [ ] Replace `_print_lifecycle_plan()` call with dedicated `_print_plan_created_output()` function - [ ] Plan Created panel: Plan ID, Phase, Action, Project, Automation, Attempt - [ ] Inputs panel: list all plan arguments and automation_profile - [ ] Actors panel: Strategy, Execution, Estimation actors - [ ] Automation panel: Profile name, Source (plan override/action/global), Read-Only flag - [ ] Context panel: Resources count/types, Indexed Files, View, Hot Token Budget - [ ] Next Steps panel: execute, status, tree commands with plan ID - [ ] Add `✓ OK Plan created` confirmation line ## Definition of Done - [ ] `agents plan use <action> <project>` outputs six panels matching the spec format - [ ] All panels show correct data from the created plan - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone None (backlog). It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-new-issue-creator

freemo added a new dependency

2026-04-06 10:30:51 +00:00

#3374 Epic: E2E Workflow Specification Tests & Code Review Tool Examples

freemo added the

Points

label

2026-04-06 10:32:28 +00:00

freemo referenced this issue

2026-04-06 10:33:32 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo referenced this issue

2026-04-06 10:34:17 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo referenced this issue

2026-04-06 10:35:53 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo commented

2026-04-06 16:18:20 +00:00

Author

Owner

TRIAGE: v3.2.0 Runtime & Sessions - Medium Priority

This automated issue identifies CLI output formatting that doesn't match spec requirements. While not blocking core functionality, it's important for user experience and spec compliance.

Rationale:

Affects user experience and spec compliance but doesn't block functionality
Plan creation works correctly, only output formatting differs from spec
Priority/Medium and MoSCoW/Should Have labels are appropriate
Should be addressed after core functionality issues are resolved

Milestone Assignment: v3.2.0 - after basic plan lifecycle works, focus on CLI/UX polish.

**TRIAGE: v3.2.0 Runtime & Sessions - Medium Priority** This automated issue identifies CLI output formatting that doesn't match spec requirements. While not blocking core functionality, it's important for user experience and spec compliance. **Rationale:** - Affects user experience and spec compliance but doesn't block functionality - Plan creation works correctly, only output formatting differs from spec - Priority/Medium and MoSCoW/Should Have labels are appropriate - Should be addressed after core functionality issues are resolved **Milestone Assignment:** v3.2.0 - after basic plan lifecycle works, focus on CLI/UX polish.

freemo referenced this issue

2026-04-06 16:43:17 +00:00

UAT: agents plan execute output uses generic plan details panel instead of spec-required execution panels (Execution, Sandbox, Strategy Summary, Progress) #4129

freemo added this to the v3.4.0 milestone

2026-04-06 17:49:00 +00:00

freemo commented

2026-04-06 18:50:36 +00:00

Author

Owner

Milestone Triage Decision: Moved to Backlog

This CLI enhancement issue has been moved out of v3.3.0 during aggressive milestone triage. While useful for user experience, it does not relate to the core focus of Corrections + Subplans + Checkpoints.

Reasoning:

v3.3.0 focus: Essential corrections, subplan management, and checkpoint functionality
This issue: CLI validation enhancement - user experience improvement
Impact: UX enhancement, not core corrections/subplans/checkpoints functionality

Will be addressed in a future milestone focused on CLI polish and user experience enhancements.

**Milestone Triage Decision: Moved to Backlog** This CLI enhancement issue has been moved out of v3.3.0 during aggressive milestone triage. While useful for user experience, it does not relate to the core focus of Corrections + Subplans + Checkpoints. **Reasoning:** - v3.3.0 focus: Essential corrections, subplan management, and checkpoint functionality - This issue: CLI validation enhancement - user experience improvement - Impact: UX enhancement, not core corrections/subplans/checkpoints functionality Will be addressed in a future milestone focused on CLI polish and user experience enhancements.

freemo removed this from the v3.4.0 milestone

2026-04-06 20:42:48 +00:00