How to Use Spec-Kit with Qwen Code CLI

[Glossardi]

Hello everyone,

I've been exploring ways to expand the usability of the Spec-Kit tool, and I've found a simple method to get it working with the Qwen code CLI. While the tool's documentation primarily mentions Gemini and GitHub Copilot, it's very easy to use with Qwen as well.

The key is a small change to a folder name. The Qwen CLI, which is forked from the Gemini CLI, looks for files in a similarly named directory.

Here's the simple trick:

1. After initializing your project with Spec-Kit, locate the hidden directory that was created. It is typically named .gemini.

2. Simply rename this folder to .qwen.

Once you've done this, the Qwen CLI will recognize the Spec-Kit project structure, and you'll be able to use all the slash commands (/specify, /plan, etc.) just as you would with the other supported CLIs.

I hope this helps others who are interested in using Spec-Kit with the Qwen ecosystem!

[odurgun]

For whom, who are using Cline/Kilo/Roo, Select Cursor option while installing the Spec-Kit, and then use @ sign to find the commands in your editor. Example: If I want /spec command, then I type @spec and select one of the options pops up. then I type the prompt. Just pay attention of the folder path of the commands when you are picking.