When using the /specify command, if the args have any apostrophe for example (let's or can't) there is an issue when the underlying powershell script runs as shown below.
had to remove the "apostrophe" for it to work correctly.
In one particular case when i was trying out the /specify command to see resolve the "apostrophe issue" it directly jumped into implementing the the features without the following the routine (/specify ==> /clarify ==> /plan ==> /tasks ==> /implement).
I am using the GPT-5 model for this.
When using the /specify command, if the args have any apostrophe for example (let's or can't) there is an issue when the underlying powershell script runs as shown below.
had to remove the "apostrophe" for it to work correctly.
In one particular case when i was trying out the /specify command to see resolve the "apostrophe issue" it directly jumped into implementing the the features without the following the routine (/specify ==> /clarify ==> /plan ==> /tasks ==> /implement).
I am using the GPT-5 model for this.