[cli-tools-test] compile: --workflow-name CLI flag undocumented/incorrect (should be --workflows)

[github-actions]

Problem Description

The compile MCP tool CLI documentation and workflow prompt examples reference --workflow-name as the flag for targeting a specific workflow, but this parameter does not exist. The correct parameter is --workflows (an array type).

When --workflow-name is passed, the tool returns a helpful error suggesting --workflows, but any automated agent or documentation that references the old flag name will fail until it reads the error.

Tool

• Tool: compile
• Command: agenticworkflows compile --workflow-name "my-workflow"

Steps to Reproduce

1. Run agenticworkflows compile --workflow-name "auto-triage-issues"
2. Observe error: Unknown parameter 'workflow-name'. Did you mean 'workflows'?

Expected Behavior

Either --workflow-name should be accepted as an alias, or all documentation and prompt examples should consistently use --workflows.

Actual Behavior

Unknown parameter 'workflow-name'. Did you mean 'workflows'?
Run 'agenticworkflows compile --help' for usage.

Environment

• Repository: github/gh-aw
• Run ID: 26705494305
• Date: 2026-05-31

Impact

• Severity: Low
• Frequency: Always (when using --workflow-name)
• Workaround: Use --workflows (array) or JSON payload: printf '{"workflows":["my-workflow"]}' | agenticworkflows compile .

Additional Context

The Daily CLI Tools Exploratory Tester prompt uses --workflow-name in its examples. The correct invocation is:

agenticworkflows compile --workflows auto-triage-issues
# or via JSON payload
printf '{"workflows":["auto-triage-issues"]}' | agenticworkflows compile .

References: §26705494305

Generated by 🧪 Daily CLI Tools Exploratory Tester · sonnet46 2.2M · ◷

• expires on Jun 7, 2026, 6:42 AM UTC