Issue Description

Type: Inconsistent terminology in command help text
Priority: Medium (confusing/inconsistent)

Problem

The CLI uses two different terms to describe the same concept across different commands:

• Some commands use "natural language action workflows"
• Other commands use "agentic workflows"

This inconsistency can confuse users about what they're working with.

Commands Using "natural language action"

1. enable command (cmd/gh-aw/main.go:88):

   Short: "Enable natural language action workflows"
   

2. disable command (cmd/gh-aw/main.go:105):

   Short: "Disable natural language action workflows and cancel any in-progress runs"
   

3. status command (pkg/cli/status.go:15):

   Short: "Show status of natural language action files and workflows"
   

Commands Using "agentic workflow"

1. run command (cmd/gh-aw/main.go:194-195)
2. logs command (pkg/cli/logs.go:302-303)
3. init command (pkg/cli/init_command.go:19-20)
4. trial command (pkg/cli/trial_command.go:60-61)
5. mcp add subcommand (pkg/cli/mcp_add.go:304-305)
6. mcp list subcommand (pkg/cli/mcp_list.go:215-216)

Suggested Fix

Use "agentic workflows" consistently across all commands because:

1. It aligns with the product name "GitHub Agentic Workflows"
2. It's used in the majority of commands
3. It's the term used in documentation and marketing

Recommended changes:

enable command:

- Short: "Enable natural language action workflows"
+ Short: "Enable agentic workflows"

disable command:

- Short: "Disable natural language action workflows and cancel any in-progress runs"
+ Short: "Disable agentic workflows and cancel any in-progress runs"

status command:

- Short: "Show status of natural language action files and workflows"
+ Short: "Show status of agentic workflows"

Files to Modify

• cmd/gh-aw/main.go (lines 88, 105)
• pkg/cli/status.go (line 15)

AI generated by CLI Consistency Checker