TL;DR:
- Initialize a new Spec Kit project.
- Rename
.geminito.qwenfor QWEN compatibility. - Use Spec Kit commands in QWEN CLI for spec-driven development.
Step-by-Step Integration Guide
Step 1: Initialize Spec Project
Create a new project directory with GitHub Spec Kit configured for QWEN Code CLI.
Option A: New Project Directory
uvx --from git+https://github.com/github/spec-kit.git specify init --ai gemini --script sh <PROJECT_NAME>cd <PROJECT_NAME>Replace <PROJECT_NAME> with your desired project name.
Option B: Current Directory
Initialize Spec Kit in your current directory.
uvx --from git+https://github.com/github/spec-kit.git specify init --ai gemini --script sh --hereStep 2: Configure QWEN Integration
After initialization, rename the .gemini directory to .qwen for QWEN CLI compatibility.
mv .gemini .qwenEither you find any reference in .specify directory or ask Qwen Code to do it:
qwen -y -p "find files in .specify that contains Gemini-related usage. Copy the syntax and adapt it for Qwen Code. Strictly edit the files, add the syntax, and don't do anything else"Now, all GitHub Spec Kit commands are available in QWEN Code CLI.
Usage Examples
Basic Spec Creation
Create a simple spec and generate a plan.
/specify Build a weather dashboard that shows current conditions and 7-day forecast for user-selected cities/plan Use React for frontend, Express.js for backend, OpenWeatherMap API for data/tasksAdvanced Research Integration
Research technologies first, then plan a complex system.
/specify Create an e-commerce platform with payment processing, inventory management, and user reviews/plan Research Stripe integration, PostgreSQL for data, Redis for caching, Docker for deploymentConstitution Compliance
Check if your spec follows simplicity rules.
/specify Build a microservice architecture with 5 servicesThe system warns about complexity and suggests fewer services.
