Roo Code Test of constitution Command Fails

Roo Code Version: 3.28.15 (7734b29c)
VSC Version: 1.104.3 Mac

Test Method
Create a new project using a command similar to `specify init sk4 --ai roo --script sh`, then select different models to execute `/speckit.constitution SOME DESCRIPTION` with Roo Code. The situation is confusing:
1. GPT-5-Codex
constitution.md is modified successfully, but at the same time, three templates in .specify/templates are also modified. I'm not sure if the latter should be modified. If they should, it means there's redundant information in the specification file. If not, it indicates that this tool does not provide read-only protection for specific files, and its prompt has factual defects.
Additionally, in my test, I used a Chinese description, so constitution.md was modified to a state mixed with Chinese and English. I'm not sure if the modified language in the section titles will affect subsequent operations.
The process consumed 400k tokens, which was somewhat unexpected.

2. Qwen3-Next-80B-A3B-Thinking
constitution.md was modified, with some content deleted, but none of the expected content was written. A total of four files in .specify/templates were modified in a similar manner.
The issue here is the same as with Claude and Qwen3 235B later: the project name and constitution requirements were not passed correctly. Since I had auto-approval enabled, the AI automatically chose to use blank values for replacement.

3. Qwen3-Coder-30B-A3B-Instruct
Unable to complete the command

4. Grok-Coder-Fast-1
Unable to complete the command

5. Claude 4.5
After consuming 120k tokens, the model asked me to provide the project name, core principles, and whether I want to create a new file or update it.

6. GPT-OSS-120B
Unable to complete the command

7. Qwen3-235B-A22B-Instruct-2507
After consuming 180k tokens, similar to Claude, it asked for the project name and core principles.

Is this tool really adapted for Roo Code?

Furthermore, writing a project's constitution content is not a high-difficulty task. Logically speaking, even relatively weak models should be capable of handling it. I'm not sure if the failure above is due to the model, Roo Code, or Spec Kit itself, but I suggest adding recommended models in the README.

Tái hiện `/speckit.constitution` bằng các model Roo Code được báo cáo, sau đó kiểm tra `constitution.md` được tạo và các thay đổi trong `.specify/templates`. Đọc README để xem hướng dẫn hiện có về model và ghi lại liệu các chỉnh sửa quan sát được, các giá trị bị thiếu, các ngôn ngữ trộn lẫn và mức sử dụng token có đúng như mong đợi hay không. Được xem là hoàn tất khi vấn đề tương thích của Roo Code được khoanh vùng vào Spec Kit, Roo Code hoặc các model, kèm hướng dẫn rõ ràng hoặc một fix tập trung.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.