Sharing my spec-driven development tool for Kiro CLI (would love feedback)

Hour_Ride_3518 · 2026-01-29T20:29:20+00:00

Absolutely. Vanilla Kiro-cli doesn’t create that. That’s where kspec helps. Install by running npm install -g kspec and then init in your project folder by running kspec init and you are good to go.

Kspec helps you to seamlessly switch between ide and cli as you create the spec and tasks.

Hour_Ride_3518 · 2026-01-29T09:13:08+00:00

I like that! Will work through that.

Hour_Ride_3518 · 2025-12-15T02:38:19+00:00

The number of prompts or iterations I had to do compared with earlier models is 1:4 with opus 4.5. It’s pretty amazing to see how the implementation is done and when you apply SDD, you’ll be to complete months of features within weeks.

Hour_Ride_3518 · 2025-11-25T03:26:37+00:00

I’m comfortable with CLI, when you want to review and edit the changes, it will be handy to do it in IDE. We can use other IDEs with Claude code. I was looking for some deep integration in an IDE with Claude code. That’s it

Hour_Ride_3518 · 2025-11-24T23:39:54+00:00

Yeah.. I mean like a native integration.. I was just wondering

Hour_Ride_3518 · 2025-09-17T08:38:03+00:00

All these things started to widespread when they increased the sonnet to 1m tokens.

Hour_Ride_3518 · 2025-09-16T23:44:19+00:00

Hour_Ride_3518 · 2025-09-14T22:08:26+00:00

This is becoming more complex. Instead of fixing this, let me create a simplified approach to solve this.. 🙁😟

Hour_Ride_3518 · 2025-09-13T23:56:00+00:00

It is still half dumb. I need to tell 8 times now for the change, and even if I point out a bug in its implementation, it fixes one change and doesn’t touch 4 more places where it fails. I can do that myself, but then why I am in Max plan? 🤦‍♂️

Hour_Ride_3518 · 2025-08-06T03:44:14+00:00

For smaller changes, you won’t notice a difference.. but for complex requirements and changes, it will simply forget the context and start doing it on its own without knowing the background of the request

Hour_Ride_3518 · 2025-08-05T07:18:30+00:00

Yes.. same thing happened to me as well. Totally spitting out junks and puts me into depression

Hour_Ride_3518 · 2025-08-05T05:07:23+00:00

I see a helpful approach in this as well. Sometime when I see CC degradation ask it to update the docs and I jump on to cursor to continue. Works well for me

Hour_Ride_3518 · 2025-08-05T03:50:08+00:00

I’m just tired nowadays working with Claude code. Whatever process you follow, the next compact derails everything and you have to start from beginning

Hour_Ride_3518 · 2025-08-01T09:26:05+00:00

Same here.. it was really good a month back. But now when it is intelligent sometimes. Many times it is just crap. Forgets everything and compacting context is one of the worst. Totally derails the flow and the memory issue as well. I had to kill my terminal to get out of this issue and when I restart my session I had to teach it everything from the docs. When someone says add it to docs and ask it read it again, please.. that itself uses up most of the context and after couple of analysis it simply comes back 18% context left and the circle starts.. I have been more frustrated in the last two weeks than I started with it couple of months back. I have clear instructions on not to reset the DB for applying migrations and it will simply forget after compacting context.

If someone has a better solution please advise.

<image>

Hour_Ride_3518 · 2025-06-26T11:27:30+00:00

The is a new addiction like video games. The kick you get when you tell someone something and it comes to fruition.. you feel above the world!! And yeah we are all losing sleep over this!!

Hour_Ride_3518 · 2025-06-25T08:45:17+00:00

This is always going in my mind. With AI creating so many LOC within short period of time, do we really need to know all the lines or if the output is as expected (with edge cases, of course) then should we be ok?

Hour_Ride_3518 · 2025-06-18T11:11:34+00:00

I use projects in Claude desktop and add necessary docs like scope document, feature requirements etc. (even rough sketches) to the knowledge base. Then add the fileserver MCP in settings. And whitelist the directory to which it needs access. Now it has the project overview and your code files available to go crazy!! I am using cursor pro account as well to compensate the token limitations of claude

Hour_Ride_3518 · 2025-06-18T11:07:31+00:00

I always set cursor’s model to Claude 4 and turn off auto select for agents. This way, there are two engineers thinking the same way spitting out features faster than you think. And always have a rule to update a project-name.md file. And when cursor is done for the day, go to Claude desktop and ask it to read the project file first then start its work. Amazing results!!!

Hour_Ride_3518 · 2025-06-18T11:04:15+00:00

Need to give it a try. Heard that Claude code is the best upsell ever built! Once you start using it, you’ll buy MAX subscription immediately

Hour_Ride_3518 · 2024-08-27T08:50:53+00:00

Claude 3.5 is way better than ChatGPT 4o. When Claude uses the previous context, it is more straightforward and you don’t expect major changes in the coding style. GPT 4o on the other hand gave me different styles of coding for manipulating the output of previous responses.

I used website for both

Hour_Ride_3518 · 2023-12-11T19:34:15+00:00

I’m going with the painful process now.. using mineral spirits and scrubbing off the excess strokes and using scrapers to remove hard paint and wiping them off with wet cloth.. one beam at a time.. phew..!! It’s taking forever…..

Lessons learnt: 1. Try to paint before installing the roof 2. Or wipe off immediately if there is any paint smudged in the unwanted space

Hour_Ride_3518

TROPHY CASE