UAT: `agents plan use` rich output missing spec-required panels — Inputs, Actors, Automation, Context, and Next Steps panels not rendered #2896

New issue

Open

opened 2026-04-05 02:45:17 +00:00 by freemo · 2 comments

freemo commented

2026-04-05 02:45:17 +00:00

Owner

Metadata

Branch: fix/m5-plan-use-rich-output-panels
Commit Message: fix(cli): render spec-required panels in agents plan use rich output
Milestone: v3.5.0
Parent Epic: #397

Background and Context

The spec (docs/specification.md §agents plan use) requires the rich output to include 6 separate panels: "Plan Created", "Inputs", "Actors", "Automation", "Context", and "Next Steps". The current implementation in src/cleveragents/cli/commands/plan.py calls _print_lifecycle_plan(plan, title="Plan Created") which renders a single monolithic panel with all fields merged together. The spec-required "Inputs", "Actors", "Automation", "Context", and "Next Steps" panels are completely absent.

Current Behavior

agents plan use renders a single panel titled "Plan Created" containing all plan fields in one block. No separate Inputs, Actors, Automation, Context, or Next Steps panels are shown.

Code location: src/cleveragents/cli/commands/plan.py, use_action() function (around line 1392), calls _print_lifecycle_plan() instead of rendering spec-required panels.

Expected Behavior

Per the spec, agents plan use must render 6 separate Rich 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

Acceptance Criteria

agents plan use <ACTION> <PROJECT> renders a "Plan Created" panel with Plan ID, Phase, Action, Project, Automation, and Attempt fields
A separate "Inputs" panel is rendered listing all input key=value pairs (or "(none)" if empty)
A separate "Actors" panel is rendered with Strategy, Execution, and Estimation actor fields
A separate "Automation" panel is rendered with Profile, Source, and Read-Only fields
A separate "Context" panel is rendered with Resources, Indexed Files, View, and Hot Token Budget fields
A separate "Next Steps" panel is rendered with suggested follow-up commands using the new plan's ID
All 6 panels appear in the correct order as specified
The final ✓ OK Plan created status line is present
JSON/YAML output formats are unaffected
All nox stages pass with coverage >= 97%

Subtasks

Audit use_action() in plan.py and identify the _print_lifecycle_plan() call to replace
Implement _print_plan_use_panels(plan) helper rendering all 6 spec-required panels
Replace the _print_lifecycle_plan() call in use_action() with the new helper
Write Behave unit tests covering each panel's content and ordering
Write Robot Framework integration test for agents plan use rich output
Verify JSON/YAML output paths are unaffected
Run nox and confirm all stages pass with coverage >= 97%

Definition of Done

All subtasks above are checked
agents plan use rich output renders all 6 spec-required panels in the correct order
Behave unit tests cover all 6 panels
Robot Framework integration test passes for rich output
Commit pushed to fix/m5-plan-use-rich-output-panels with message fix(cli): render spec-required panels in agents plan use rich output
PR merged and issue closed
All nox stages pass
Coverage >= 97%

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

## Metadata - **Branch**: `fix/m5-plan-use-rich-output-panels` - **Commit Message**: `fix(cli): render spec-required panels in agents plan use rich output` - **Milestone**: v3.5.0 - **Parent Epic**: #397 ## Background and Context The spec (`docs/specification.md` §agents plan use) requires the rich output to include 6 separate panels: "Plan Created", "Inputs", "Actors", "Automation", "Context", and "Next Steps". The current implementation in `src/cleveragents/cli/commands/plan.py` calls `_print_lifecycle_plan(plan, title="Plan Created")` which renders a single monolithic panel with all fields merged together. The spec-required "Inputs", "Actors", "Automation", "Context", and "Next Steps" panels are completely absent. ## Current Behavior `agents plan use` renders a single panel titled "Plan Created" containing all plan fields in one block. No separate Inputs, Actors, Automation, Context, or Next Steps panels are shown. **Code location**: `src/cleveragents/cli/commands/plan.py`, `use_action()` function (around line 1392), calls `_print_lifecycle_plan()` instead of rendering spec-required panels. ## Expected Behavior Per the spec, `agents plan use` must render 6 separate Rich 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 ``` ## Acceptance Criteria - [ ] `agents plan use <ACTION> <PROJECT>` renders a "Plan Created" panel with Plan ID, Phase, Action, Project, Automation, and Attempt fields - [ ] A separate "Inputs" panel is rendered listing all input key=value pairs (or "(none)" if empty) - [ ] A separate "Actors" panel is rendered with Strategy, Execution, and Estimation actor fields - [ ] A separate "Automation" panel is rendered with Profile, Source, and Read-Only fields - [ ] A separate "Context" panel is rendered with Resources, Indexed Files, View, and Hot Token Budget fields - [ ] A separate "Next Steps" panel is rendered with suggested follow-up commands using the new plan's ID - [ ] All 6 panels appear in the correct order as specified - [ ] The final `✓ OK Plan created` status line is present - [ ] JSON/YAML output formats are unaffected - [ ] All nox stages pass with coverage >= 97% ## Subtasks - [ ] Audit `use_action()` in `plan.py` and identify the `_print_lifecycle_plan()` call to replace - [ ] Implement `_print_plan_use_panels(plan)` helper rendering all 6 spec-required panels - [ ] Replace the `_print_lifecycle_plan()` call in `use_action()` with the new helper - [ ] Write Behave unit tests covering each panel's content and ordering - [ ] Write Robot Framework integration test for `agents plan use` rich output - [ ] Verify JSON/YAML output paths are unaffected - [ ] Run `nox` and confirm all stages pass with coverage >= 97% ## Definition of Done - [ ] All subtasks above are checked - [ ] `agents plan use` rich output renders all 6 spec-required panels in the correct order - [ ] Behave unit tests cover all 6 panels - [ ] Robot Framework integration test passes for rich output - [ ] Commit pushed to `fix/m5-plan-use-rich-output-panels` with message `fix(cli): render spec-required panels in agents plan use rich output` - [ ] PR merged and issue closed - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-new-issue-creator

freemo added this to the v3.5.0 milestone

2026-04-05 02:46:51 +00:00

freemo added a new dependency

2026-04-05 02:47:00 +00:00

#397 Epic: Server & Autonomy Infrastructure

freemo commented

2026-04-05 02:53:02 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium (confirmed)
MoSCoW: Should Have — rich output panels missing per spec

Valid UAT finding verified during batch triage.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium (confirmed) - **MoSCoW**: Should Have — rich output panels missing per spec Valid UAT finding verified during batch triage. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo commented

2026-04-06 22:48:24 +00:00

Author

Owner

This issue has been moved to the backlog as part of an aggressive grooming of the v3.5.0 milestone. It has been deemed non-critical for the minimal viability of the milestone and will be addressed in a future release.