Bug Description
When running the .specify/scripts/powershell/create-new-feature.ps1 script using the /speckit.specify command via gemini-cli, a ParameterBindingArgumentTransformationException error occurs on the initial run. This is because the script attempts to incorrectly bind a positional string argument (feature description) to a Number parameter of type Int32.
Steps to Reproduce
- Run gemini-cli in a Windows environment.
- Execute the /speckit.specify command and provide a feature description (e.g., '링크를 입력하면 웹페이지의 내용을 읽어와 md로 저장하는 기능').
- The CLI attempts to execute the create-new-feature.ps1 script using positional arguments.
- Observe the error log on the first attempt.
Expected Behavior
The create-new-feature.ps1 script should properly map an unnamed positional string to the appropriate description/title parameter, or strictly enforce named parameters without failing outright by trying to cast a descriptive text string to Int32.
Actual Behavior
The script fails on the initial attempt because PowerShell binds the description string to the $Number parameter.
Interestingly, gemini-cli automatically catches this failure and intelligently retries the execution by explicitly naming the parameters (passing -Number 0). The second attempt succeeds, and the branch is created.
Specify CLI Version
0.3.0
AI Agent
Gemini CLI
Operating System
Windows 10.0.26200 AMD64
Python Version
3.11.4
Error Logs
Cannot process argument transformation on parameter 'Number'. Cannot convert value "링크를 입력하면 웹페이지의 내용을 읽어와 md로 저장하는 기능" to type "System.Int32". Error: "Input string was not in a correct format."
At line:1 char:52
+ ... l/create-new-feature.ps1 '링크를 입력하면 웹페이지의 내용을 읽어와 md로 저장하는 기능' -Json - ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [create-new-feature.ps1], ParameterBindingArgumentTransformationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,create-new-feature.ps1
Additional Context
Thanks to gemini-cli's automatic retry mechanism, the feature branch (001-save-url-as-md) is ultimately created, but it is inconvenient that an exception log is displayed every time it is run for the first time.
I have a few questions for the administrators.
Is this an isolated issue specific to my setup, or is it a known behavior that occurs when the AI agent interacts with this script?
Do you plan to modify the Param() block in create-new-feature.ps1 (e.g., adjusting the position attribute) to prevent errors from occurring on the first call from the CLI?