troubles with workflow: Codex Cli commands don't accept arguments

[edelah]

This simple workflow example, taken from your documentation is not feasable currently with Codex Cli.
/plan or /specify ignore aguments.

It makes the use of Spec Kit impratical currently.

 # Step 1: Create the feature specification (5 minutes)
 /specify Real-time chat system with message history and user presence
 
 # This automatically:
 # - Creates branch "003-chat-system"
 # - Generates specs/003-chat-system/spec.md
 # - Populates it with structured requirements
 
 # Step 2: Generate implementation plan (5 minutes)
 /plan WebSocket for real-time messaging, PostgreSQL for history, Redis for presence
 
 # Step 3: Generate executable tasks (5 minutes)
 /tasks
 
 # This automatically creates:
 # - specs/003-chat-system/plan.md
 # - specs/003-chat-system/research.md (WebSocket library comparisons)
 # - specs/003-chat-system/data-model.md (Message and User schemas)
 # - specs/003-chat-system/contracts/ (WebSocket events, REST endpoints)
 # - specs/003-chat-system/quickstart.md (Key validation scenarios)
 # - specs/003-chat-system/tasks.md (Task list derived from the plan)

[localden]

I agree, but that's definitely an external-sourced issue that we have no control over at this time.

See warning in Specify:

This is all dependent on the resolution of openai/codex#2890.