Gemini fail to recognize commands after spec kit initialization

[ktfth]

The generation based on gemini cli template fail to recognize all commands on windows 11. The configuration cause a problem at all, to reproduce this is just needed to start a project using gemini cli option and the error happens.

[Aiyatullah]

Hey brother have you found any solution to it? facing the same issue

[ferquo]

Did you guys initialize in an existing project? In this case use --here instead of providing a name

[ktfth]

I facing an issue just using the main way to initialize the project.

[voducdan]

I face the same issue on ubuntu. After initializing project using specify init and run gemini, commands likes /specify, /plan, and /task do not exist.

[localden]

It takes a few seconds for Gemini CLI to "warm up" and make the commands available. Can you folks confirm that is the case for you?

[voducdan]

It takes a few seconds for Gemini CLI to "warm up" and make the commands available. Can you folks confirm that is the case for you?

I still cannot see /specify after an hour. You can see output of "ls" command to ensure that this folder is created by spec-kit.

[aprendendofelipe]

Have you tried updating the Gemini CLI?

npm install -g @google/gemini-cli@latest

[ktfth]

Updated the cli but still buggy, this seems to be a gemini cli problem not a thing on spec kit at all.

[ktfth]

This week I have the time to confirm and the Gemini cli worked again. I'm gonna retest the spec kit.