feat(cli): add plan explain and decision tree outputs #174

Closed
opened 2026-02-22 23:39:50 +00:00 by freemo · 1 comment
Owner

Metadata

  • Commit Message: feat(cli): add plan explain and decision tree outputs
  • Branch: feature/m4-decision-cli

Background

The CLI provides plan explain and plan tree commands that format decision trees in json/yaml/table formats. Flags control views for superseded decisions, context snapshots, and reasoning details.

Acceptance Criteria

  • Add plan explain and plan tree CLI output with decision tree formatting (json/yaml/table) and flags for superseded/context/reasoning views.
  • Update docs/reference/plan_cli.md with explain/tree examples.

Definition of Done

This issue is complete when:

  • All subtasks below are completed and checked off.
  • A Git commit is created where the first line of the commit message matches
    the Commit Message in Metadata exactly, followed by a blank line, then
    additional lines providing relevant details about the implementation. The
    commit body should be appropriate in size for a commit message and relatively
    complete in describing what was done.
  • The commit is pushed to the remote on the branch matching the Branch in
    Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and
    merged before this issue is marked done.

Subtasks

  • Add plan explain and plan tree CLI output with decision tree formatting (json/yaml/table) and flags for superseded/context/reasoning views.
  • Update docs/reference/plan_cli.md with explain/tree examples.
  • Tests (Behave): Add scenarios for explain/tree output in multiple formats.
  • Tests (Robot): Add Robot CLI test for plan explain output fields.
  • Tests (ASV): Add benchmarks/plan_explain_bench.py for output generation.
  • Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: #### M3: Decisions + Validations + Invariants (Day 18)
Status: Open

## Metadata - **Commit Message**: `feat(cli): add plan explain and decision tree outputs` - **Branch**: `feature/m4-decision-cli` ## Background The CLI provides `plan explain` and `plan tree` commands that format decision trees in json/yaml/table formats. Flags control views for superseded decisions, context snapshots, and reasoning details. ## Acceptance Criteria - [ ] Add `plan explain` and `plan tree` CLI output with decision tree formatting (json/yaml/table) and flags for superseded/context/reasoning views. - [ ] Update `docs/reference/plan_cli.md` with explain/tree examples. ## Definition of Done This issue is complete when: - All subtasks below are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. The commit body should be appropriate in size for a commit message and relatively complete in describing what was done. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. ## Subtasks - [ ] Add `plan explain` and `plan tree` CLI output with decision tree formatting (json/yaml/table) and flags for superseded/context/reasoning views. - [ ] Update `docs/reference/plan_cli.md` with explain/tree examples. - [ ] Tests (Behave): Add scenarios for explain/tree output in multiple formats. - [ ] Tests (Robot): Add Robot CLI test for `plan explain` output fields. - [ ] Tests (ASV): Add `benchmarks/plan_explain_bench.py` for output generation. - [ ] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: #### M3: Decisions + Validations + Invariants (Day 18) **Status**: Open
freemo added this to the v3.2.0 milestone 2026-02-22 23:39:50 +00:00
Author
Owner

Expected completion updated (Day 15 rebaseline): Day 29 / 2026-03-09 (previously Day 21 / 2026-03-01)

**Expected completion updated (Day 15 rebaseline):** Day 29 / 2026-03-09 (previously Day 21 / 2026-03-01)
freemo added the due date 2026-02-28 2026-02-23 18:41:26 +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".

2026-02-28

Reference
cleveragents/cleveragents-core#174
No description provided.