cleveragents/cleveragents-core

Fork 3

UAT: `agents plan use` rich output uses generic single panel instead of spec-required multi-panel layout #6044

New issue

Open

opened 2026-04-09 14:03:50 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-09 14:03:50 +00:00

Owner

Summary

agents plan use rich output uses the generic _print_lifecycle_plan() function which renders a single flat panel. The specification requires a structured multi-panel layout with 6 distinct panels.

Expected Behavior (from spec §agents plan use)

The spec defines the following rich output panels:

╭─ Plan Created ──────────────────────╮
│ Plan ID: 01HXM8C2ZK4Q7C2B3F2R4VYV6J │
│ Phase: strategize                   │
│ Action: local/code-coverage         │
│ Project: local/api-service          │
│ Automation: trusted                 │
│ Attempt: 1                          │
╰─────────────────────────────────────╯

╭─ Inputs ──────────────────────╮
│ - target_coverage_percent=85  │
│ - automation_profile=trusted  │
╰───────────────────────────────╯

╭─ Actors ────────────────────────╮
│ Strategy: local/strategist      │
│ Execution: local/executor       │
│ Estimation: (none)              │
╰─────────────────────────────────╯

╭─ Automation ─────────────────────────╮
│ Profile: trusted                     │
│ Source: CLI flag                     │
│ Read-Only: no                        │
╰──────────────────────────────────────╯

╭─ Context ───────────────────────╮
│ Resources: 2 (repo, db)         │
│ Indexed Files: 347              │
│ View: strategize                │
│ Hot Token Budget: 12,000        │
╰─────────────────────────────────╯

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

✓ OK Plan created

Actual Behavior

The implementation calls _print_lifecycle_plan(plan, title="Plan Created") which renders a single generic panel with fields like ID, Name, Action, Phase, Processing State, Projects, Description, Strategy Actor, Execution Actor, etc. Followed by a dim hint: Plan is now in Strategize phase (queued). Run 'agents plan execute <id>' when ready.

Missing panels:

Inputs panel (showing --arg values and --automation-profile)
Actors panel (separate panel for Strategy/Execution/Estimation actors)
Automation panel (Profile, Source, Read-Only)
Context panel (Resources, Indexed Files, View, Hot Token Budget)
Next Steps panel (with specific plan ID commands)
✓ OK Plan created success message

Code Location

src/cleveragents/cli/commands/plan.py, use_action() function (~line 1915):

_print_lifecycle_plan(plan, title="Plan Created")

Steps to Reproduce

agents plan use local/some-action local/some-project

Impact

The rich output does not match the spec-defined UX contract. Users miss important context (next steps, actor overrides, context stats). Downstream automation that parses rich output may also be affected.

Subtasks

Implement _print_plan_created_panels() helper that renders the 6-panel layout
Replace _print_lifecycle_plan(plan, title="Plan Created") call in use_action() with the new helper
Add ✓ OK Plan created success message
Add Next Steps panel with plan-ID-specific commands

Definition of Done

agents plan use rich output shows all 6 panels as specified
✓ OK Plan created message is printed
Next Steps panel includes the correct plan ID in suggested commands

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Summary `agents plan use` rich output uses the generic `_print_lifecycle_plan()` function which renders a single flat panel. The specification requires a structured multi-panel layout with 6 distinct panels. ## Expected Behavior (from spec §agents plan use) The spec defines the following rich output panels: ``` ╭─ Plan Created ──────────────────────╮ │ Plan ID: 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ │ Phase: strategize │ │ Action: local/code-coverage │ │ Project: local/api-service │ │ Automation: trusted │ │ Attempt: 1 │ ╰─────────────────────────────────────╯ ╭─ Inputs ──────────────────────╮ │ - target_coverage_percent=85 │ │ - automation_profile=trusted │ ╰───────────────────────────────╯ ╭─ Actors ────────────────────────╮ │ Strategy: local/strategist │ │ Execution: local/executor │ │ Estimation: (none) │ ╰─────────────────────────────────╯ ╭─ Automation ─────────────────────────╮ │ Profile: trusted │ │ Source: CLI flag │ │ Read-Only: no │ ╰──────────────────────────────────────╯ ╭─ Context ───────────────────────╮ │ Resources: 2 (repo, db) │ │ Indexed Files: 347 │ │ View: strategize │ │ Hot Token Budget: 12,000 │ ╰─────────────────────────────────╯ ╭─ Next Steps ─────────────────────────────────────╮ │ - agents plan execute 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ │ - agents plan status 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ │ - agents plan tree 01HXM8C2ZK4Q7C2B3F2R4VYV6J │ ╰──────────────────────────────────────────────────╯ ✓ OK Plan created ``` ## Actual Behavior The implementation calls `_print_lifecycle_plan(plan, title="Plan Created")` which renders a single generic panel with fields like `ID`, `Name`, `Action`, `Phase`, `Processing State`, `Projects`, `Description`, `Strategy Actor`, `Execution Actor`, etc. Followed by a dim hint: `Plan is now in Strategize phase (queued). Run 'agents plan execute <id>' when ready.` Missing panels: - **Inputs** panel (showing `--arg` values and `--automation-profile`) - **Actors** panel (separate panel for Strategy/Execution/Estimation actors) - **Automation** panel (Profile, Source, Read-Only) - **Context** panel (Resources, Indexed Files, View, Hot Token Budget) - **Next Steps** panel (with specific plan ID commands) - **`✓ OK Plan created`** success message ## Code Location `src/cleveragents/cli/commands/plan.py`, `use_action()` function (~line 1915): ```python _print_lifecycle_plan(plan, title="Plan Created") ``` ## Steps to Reproduce ```bash agents plan use local/some-action local/some-project ``` ## Impact The rich output does not match the spec-defined UX contract. Users miss important context (next steps, actor overrides, context stats). Downstream automation that parses rich output may also be affected. ## Subtasks - [ ] Implement `_print_plan_created_panels()` helper that renders the 6-panel layout - [ ] Replace `_print_lifecycle_plan(plan, title="Plan Created")` call in `use_action()` with the new helper - [ ] Add `✓ OK Plan created` success message - [ ] Add `Next Steps` panel with plan-ID-specific commands ## Definition of Done - `agents plan use` rich output shows all 6 panels as specified - `✓ OK Plan created` message is printed - `Next Steps` panel includes the correct plan ID in suggested commands --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 14:18:03 +00:00

HAL9000 referenced this issue

2026-04-09 14:24:09 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 35) #6073

HAL9000 added this to the v3.2.0 milestone

2026-04-09 14:31:49 +00:00

HAL9000 added a new dependency

2026-04-09 14:37:24 +00:00

#4958 EPIC: Decision Recording & Tree Visualization — Plan Decisions Persisted to DB

HAL9000 commented

2026-04-09 14:40:50 +00:00

Author

Owner

Label compliance fix applied:

Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 referenced this issue

2026-04-09 15:13:55 +00:00

[AUTO-EPIC] Epic Planning Health Report (Cycle 21) #5883

HAL9000 added

and removed

labels

2026-04-09 15:23:58 +00:00

HAL9000 modified the milestone from v3.2.0 to v3.3.0

2026-04-09 15:23:59 +00:00

HAL9000 commented

2026-04-09 15:50:23 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium — agents plan use rich output uses a generic single panel instead of the spec-required multi-panel layout with 6 distinct panels. This is a UX deviation.
Milestone: v3.3.0 — Plan display is part of the Corrections + Subplans + Checkpoints milestone deliverables.
Story Points: 3 — M — Implementing the 6-panel layout requires refactoring the rich output rendering for the plan use command.
MoSCoW: Should Have — The spec defines a specific multi-panel layout. Should be implemented for spec compliance, but doesn't block core plan execution.
Parent Epic: Needs linking to the Plan Lifecycle epic.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium — `agents plan use` rich output uses a generic single panel instead of the spec-required multi-panel layout with 6 distinct panels. This is a UX deviation. - **Milestone**: v3.3.0 — Plan display is part of the Corrections + Subplans + Checkpoints milestone deliverables. - **Story Points**: 3 — M — Implementing the 6-panel layout requires refactoring the rich output rendering for the `plan use` command. - **MoSCoW**: Should Have — The spec defines a specific multi-panel layout. Should be implemented for spec compliance, but doesn't block core plan execution. - **Parent Epic**: Needs linking to the Plan Lifecycle epic. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner