Use Spec Kitty in Qwen Code
Who is this for (1)
- Stakeholder Persona: Project Owner — Written for the Project Owner reader.
Tier: supported. Citation (accessed 2026-05-21): https://github.com/QwenLM/qwen-code
Prerequisites
- Spec Kitty CLI installed. See Install Spec Kitty.
- Project initialized for this harness:
Terminal window spec-kitty init --ai qwen - Qwen Code installed and authenticated. Follow the QwenLM/qwen-code README for installation and authentication.
Where Spec Kitty installs files
Per the supported-harnesses matrix, Qwen Code uses the slash-command mechanism. Spec Kitty installs:
- Directory:
.qwen/commands/ - Files:
spec-kitty.specify.md,spec-kitty.plan.md,spec-kitty.tasks.md,spec-kitty.implement.md,spec-kitty.review.md,spec-kitty.accept.md,spec-kitty.merge.md,spec-kitty.status.md,spec-kitty.charter.md,spec-kitty.analyze.md,spec-kitty.research.md.
Canonical invocation
Inside Qwen Code, slash commands are invoked as:
/spec-kitty.specify "<one-line mission description>"/spec-kitty.plan/spec-kitty.tasks/spec-kitty.implement WP01Worked example
- From your project root, launch Qwen Code.
- At the prompt, type:
/spec-kitty.specify "a hello world page"
- Spec Kitty’s interview prompts appear — answer them inline.
- When asked for a kebab-case slug, supply something short, e.g.
hello-world-page. - The mission spec lands at
kitty-specs/hello-world-page-<mid8>/spec.md.
Troubleshooting
-
/spec-kitty.*commands do not appear. Runspec-kitty agent config syncfrom the repo root. This rewrites.qwen/commands/from the canonical source templates. Restart Qwen Code. -
Profile not loading. Run inside Qwen Code:
/spk-charter-profile-load researcher-robbieUse the profile id from the work-package frontmatter.
Where to learn more about Qwen Code
Authoritative documentation: https://github.com/QwenLM/qwen-code (accessed 2026-05-21).