HAL9000
bb428fc69b
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Failing after 45s
CI / push-validation (pull_request) Successful in 23s
CI / quality (pull_request) Successful in 1m9s
CI / security (pull_request) Successful in 1m19s
CI / helm (pull_request) Successful in 39s
CI / typecheck (pull_request) Failing after 1m23s
CI / benchmark-regression (pull_request) Failing after 1m2s
CI / build (pull_request) Successful in 53s
CI / e2e_tests (pull_request) Failing after 1m18s
CI / integration_tests (pull_request) Failing after 3m18s
CI / unit_tests (pull_request) Failing after 49m8s
CI / docker (pull_request) Has been cancelled
CI / coverage (pull_request) Has been cancelled
CI / status-check (pull_request) Has been cancelled
Add 'start' as an alias for the 'plan use' CLI command. Both 'agents plan start <action> <project>' and 'agents plan use <action> <project>' create a plan in the Strategize phase with identical arguments and options. Includes updated help text, BDD test coverage, CHANGELOG.md entry, and CONTRIBUTORS.md update. Closes #8661 ISSUES CLOSED: #8661
27 lines
1.2 KiB
Gherkin
27 lines
1.2 KiB
Gherkin
Feature: Plan start alias CLI coverage
|
|
As a developer
|
|
I want ``agents plan start`` to be available as an alias for ``plan use``
|
|
So that users can more intuitively create plans from action templates
|
|
|
|
Background:
|
|
Given a plan lifecycle CLI runner
|
|
And a mocked lifecycle service for plan commands
|
|
|
|
Scenario: Plan start creates a plan (alias for plan use)
|
|
When I run plan lifecycle command "start" with action "local/code-coverage"
|
|
Then the plan lifecycle command should succeed
|
|
And the plan lifecycle output should contain "Strategize phase"
|
|
And the plan lifecycle use service should be invoked
|
|
|
|
Scenario: Plan start accepts --arg flag (alias for plan use)
|
|
When I run plan lifecycle command "start" with action "local/code-coverage"
|
|
Then the plan lifecycle command should succeed
|
|
|
|
Scenario: Plan start with --automation-profile flag (alias for plan use)
|
|
When I run plan lifecycle command "start" with action "local/code-coverage"
|
|
Then the plan lifecycle command should succeed
|
|
|
|
Scenario: Plan start accepts multiple projects (alias for plan use)
|
|
When I run plan lifecycle command "start" with action "local/security-audit"
|
|
Then the plan lifecycle command should succeed
|