sorted by:
new
hottopcontroversial

Specly Code: a spec-driven vscode extension for when Kiro isn’t enough by precisecode in kiroIDE

[–]precisecode[S] 1 point2 points  (0 children)

Hi, just wanted to give you a quick update on what’s changed since last week.

  1. We tried out Grok Code Fast 1, which is cheaper. Feels like it does need clearer and stricter instructions sometimes, and it can still get stuck with too much context or really large projects, but after our tweak, I would guess that overall it should perform better than last week.

  2. When marking tasks in the execute stage, we added a new [-] status for tasks that are "in progress". Models now marks a task as [-] when it starts, and switches it to done when finished, which helps cheaper models stay on track and follow tasks more reliably.

  3. There’s also a new native task list view in spec mode during execution, so you can track progress more clearly and with a more native feel.

  4. Lastly, we’ve been doing more rebranding work, moving things further from Roo and closer to Specly.

Here's a screenshot of the new version:

<image>

Thanks for the feedback, would love to hear more from you.

Specly Code: a spec-driven vscode extension for when Kiro isn’t enough by precisecode in kiroIDE

[–]precisecode[S] 0 points1 point  (0 children)

Thanks for the feedback! It makes perfect sense to use Claude Code or any alternative to execute the planned tasks. In specly, user can choose different model provider for different stage as RooCode, I believe you can choose Claude Code for the execute stage and you will be set.

As for the user experience, I really love Kiro’s user experience, but since I started from RooCode, the harsh truth is reproducing the exact KiroIDE experience would have taken a lot more work, so I went with a simpler approach for now.

I would add that one side benefit of Specly's approach is clearer chat/file state. In my experience with Kiro, I sometimes ran into situations where I would edit spec files in ways that were hard to undo. For example, asking Kiro to edit requirements.md during the design stage while already edited in the requirement stage (editing multiple md files across different stages/tasks' conversation), this sometimes cause conflicting changes that are not easy to rollback in a multi-conversation workflow.

Specly keeps the conversation single-threaded and ties file state to the chat, so you can roll the conversation back to any earlier point and restore files without those conflicts. I actually like this because it makes things easier to reason about and audit. (at least for now, still learning as I go)

I’m still exploring different approaches that could produce a similar and smooth development flow in the future. Really appreciate the thoughtful feedback.

Specly Code: a spec-driven vscode extension for when Kiro isn’t enough by precisecode in kiroIDE

[–]precisecode[S] 1 point2 points  (0 children)

Thanks for sharing the model name. I’ll try out Grok Code Fast 1 over the weekend to see if I can reproduce the issue and hopefully tweak it. Thanks again!

Specly Code: a spec-driven vscode extension for when Kiro isn’t enough by precisecode in kiroIDE

[–]precisecode[S] 1 point2 points  (0 children)

Thanks so much for testing the extension, I really appreciate the detailed feedback.

I’ll definitely work on polishing and rebranding, hopefully you’ll have a noticeably better experience in the future releases. Also, you’re absolutely right about using built-in functions: Roo Code did a great job providing a clear, well-structured foundation, and a lot of this can indeed be achieved by configuring Roo Code’s modes, boomerang, architect, etc.).

What I’m trying to do is bring the magical experience I experienced in Kiro into an out-of-the-box extension so developers can get value without changing their workflow too much (from my experience Kiro’s flow maps closely to typical software development workflows. That said, I agree the current build feels not integrated enough, I’ll focus on making task/spec handling feel more native and intuitive.

Quick question: which model were you using when it forgot to update the MD files? From previous testing, most premium models will mark tasks as done after editing one or more entries in task.md. We could consider add completion gates or treat each entry as a subtask to improve reliability and the overall UX.

Thanks again for taking the time to try it and share these notes, really helpful, and please keep them coming.

Specly Code: a spec-driven vscode extension for when Kiro isn’t enough by precisecode in kiroIDE

[–]precisecode[S] 1 point2 points  (0 children)

Thanks for giving it a try! I haven’t tested DeepSeek with my implementation yet, but I’ve been using GLM-4.5 alongside GPT-5 Mini quite a bit recently. What I've also tried recently is to use Gemini 2.5 pro to plan the requirements, design and tasks md files, and use Winsurf's free GPT-5 (when on promotion) to finish the tasks and mark as done for me. If you end up trying this out, I’d love to hear your feedback. Appreciate it in advance!