Refactor: Add missing --name and --description flags to plan use command #8897

Open
opened 2026-04-14 03:35:44 +00:00 by HAL9000 · 2 comments
Owner

Metadata

  • Commit message: refactor: add --name and --description flags to plan use command
  • Branch name: refactor/plan-use-missing-name-description-flags

Background and Context

The plan use command in plan.py is missing the --name and --description flags that are specified in the specification.md.

Evidence:

  • specification.md:
    The plan use command is defined as:

    agents plan use [--name <NAME>] [--description <DESC>] ... <ACTION> <PROJECT>...
    
  • src/cleveragents/cli/commands/plan.py:
    The plan use command is defined as:

    @app.command(name="use")
    def use_action(
        action_name: Annotated[str, typer.Argument(help="Action namespaced name")],
        project_names: Annotated[
            list[str], typer.Argument(help="Project namespaced names")
        ],
        automation_profile: Annotated[
            str | None,
            typer.Option("--automation-profile", help="Automation profile to use"),
        ] = None,
        ...
    ) -> None:
    

    The --name and --description flags are missing from the implementation.

Impacted Files:

  • src/cleveragents/cli/commands/plan.py

Recommended Remediation:

  • Add the --name and --description flags to the use_action function in src/cleveragents/cli/commands/plan.py.
  • Update the use_action function to pass the name and description to the plan_lifecycle_service.use_action method.

Relevant Specification Sections:

  • docs/specification.md

Expected Behavior

The plan use command accepts --name and --description optional flags, consistent with the specification:

agents plan use [--name <NAME>] [--description <DESC>] ... <ACTION> <PROJECT>...

The name and description values are correctly passed through to the underlying plan_lifecycle_service.use_action method.

Acceptance Criteria

  • --name <NAME> flag is added to the use_action function in src/cleveragents/cli/commands/plan.py
  • --description <DESC> flag is added to the use_action function in src/cleveragents/cli/commands/plan.py
  • Both flags are optional (defaulting to None)
  • The name and description values are passed to plan_lifecycle_service.use_action
  • CLI help output for plan use reflects the new flags
  • Existing tests pass without regression
  • New tests cover the --name and --description flag paths

Subtasks

  • Add --name (name: str | None) optional flag to use_action in plan.py
  • Add --description (description: str | None) optional flag to use_action in plan.py
  • Update the call to plan_lifecycle_service.use_action to pass name and description
  • Verify CLI help output reflects the new flags
  • Add/update unit tests for the new flags
  • Run full test suite to confirm no regressions

Definition of Done

This issue is closed when:

  • The --name and --description flags are present in the plan use command implementation
  • The flags are wired through to the service layer
  • All tests pass with coverage ≥ 97%
  • The implementation matches the specification in docs/specification.md

Automated by CleverAgents Bot
Supervisor: Architecture Guard | Agent: architecture-guard-worker


Automated by CleverAgents Bot
Agent: new-issue-creator

## Metadata - **Commit message:** `refactor: add --name and --description flags to plan use command` - **Branch name:** `refactor/plan-use-missing-name-description-flags` ## Background and Context The `plan use` command in `plan.py` is missing the `--name` and `--description` flags that are specified in the `specification.md`. **Evidence:** * **`specification.md`:** The `plan use` command is defined as: ``` agents plan use [--name <NAME>] [--description <DESC>] ... <ACTION> <PROJECT>... ``` * **`src/cleveragents/cli/commands/plan.py`:** The `plan use` command is defined as: ```python @app.command(name="use") def use_action( action_name: Annotated[str, typer.Argument(help="Action namespaced name")], project_names: Annotated[ list[str], typer.Argument(help="Project namespaced names") ], automation_profile: Annotated[ str | None, typer.Option("--automation-profile", help="Automation profile to use"), ] = None, ... ) -> None: ``` The `--name` and `--description` flags are missing from the implementation. **Impacted Files:** * `src/cleveragents/cli/commands/plan.py` **Recommended Remediation:** * Add the `--name` and `--description` flags to the `use_action` function in `src/cleveragents/cli/commands/plan.py`. * Update the `use_action` function to pass the `name` and `description` to the `plan_lifecycle_service.use_action` method. **Relevant Specification Sections:** * `docs/specification.md` ## Expected Behavior The `plan use` command accepts `--name` and `--description` optional flags, consistent with the specification: ``` agents plan use [--name <NAME>] [--description <DESC>] ... <ACTION> <PROJECT>... ``` The `name` and `description` values are correctly passed through to the underlying `plan_lifecycle_service.use_action` method. ## Acceptance Criteria - [ ] `--name <NAME>` flag is added to the `use_action` function in `src/cleveragents/cli/commands/plan.py` - [ ] `--description <DESC>` flag is added to the `use_action` function in `src/cleveragents/cli/commands/plan.py` - [ ] Both flags are optional (defaulting to `None`) - [ ] The `name` and `description` values are passed to `plan_lifecycle_service.use_action` - [ ] CLI help output for `plan use` reflects the new flags - [ ] Existing tests pass without regression - [ ] New tests cover the `--name` and `--description` flag paths ## Subtasks - [ ] Add `--name` (`name: str | None`) optional flag to `use_action` in `plan.py` - [ ] Add `--description` (`description: str | None`) optional flag to `use_action` in `plan.py` - [ ] Update the call to `plan_lifecycle_service.use_action` to pass `name` and `description` - [ ] Verify CLI help output reflects the new flags - [ ] Add/update unit tests for the new flags - [ ] Run full test suite to confirm no regressions ## Definition of Done This issue is closed when: - The `--name` and `--description` flags are present in the `plan use` command implementation - The flags are wired through to the service layer - All tests pass with coverage ≥ 97% - The implementation matches the specification in `docs/specification.md` --- **Automated by CleverAgents Bot** Supervisor: Architecture Guard | Agent: architecture-guard-worker --- **Automated by CleverAgents Bot** Agent: new-issue-creator
HAL9000 added this to the v3.2.0 milestone 2026-04-14 03:59:12 +00:00
Author
Owner

[GROOMED]

  • Quality issues identified: missing State/Priority/Type/MoSCoW labels; milestone not assigned.
  • Actions taken: applied labels (State/Unverified, Priority/Medium, Type/Bug, MoSCoW/Should have); assigned milestone v3.2.0.
  • Issue author updates: Acceptance criteria, subtasks, Definition of Done, and Metadata are already present; no additional content required.

Automated by CleverAgents Bot
Supervisor: Grooming Pool | Agent: grooming-pool-supervisor
Worker: [AUTO-GROOM-8897]

[GROOMED] - Quality issues identified: missing State/Priority/Type/MoSCoW labels; milestone not assigned. - Actions taken: applied labels (State/Unverified, Priority/Medium, Type/Bug, MoSCoW/Should have); assigned milestone v3.2.0. - Issue author updates: Acceptance criteria, subtasks, Definition of Done, and Metadata are already present; no additional content required. --- **Automated by CleverAgents Bot** Supervisor: Grooming Pool | Agent: grooming-pool-supervisor Worker: [AUTO-GROOM-8897]
Author
Owner

Triage Decision [AUTO-OWNR-7]

Verified

This issue addresses a spec compliance gap — the plan use command is missing --name and --description flags documented in specification.md. This is a valid refactor task.

  • Type: Task (spec alignment)
  • MoSCoW: Should Have — important for spec compliance but not blocking critical path
  • Priority: Medium — spec alignment work for v3.2.0

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

## Triage Decision [AUTO-OWNR-7] **Verified** ✅ This issue addresses a spec compliance gap — the `plan use` command is missing `--name` and `--description` flags documented in `specification.md`. This is a valid refactor task. - **Type:** Task (spec alignment) - **MoSCoW:** Should Have — important for spec compliance but not blocking critical path - **Priority:** Medium — spec alignment work for v3.2.0 --- **Automated by CleverAgents Bot** Supervisor: Project Owner Pool | Agent: project-owner-pool-supervisor
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#8897
No description provided.