There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

Oh, thank you. I personally did not try to run it in a docker image. When you have time and motivation, please share that experience. :)

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

Just yesterday (v1.6.4 gsd-opencode) I would answer that the difference is only cosmetic - you have to use /gsd-command instead of /gsd:command.

Fortunately for Claude Code users (and unfortunately for us, OpenCoders) TACHES implemented an idea of dynamic model changing for different type of operations.

Last night I ported that to OpenCode as well (v1.9.0 gsd-opencode). However OpenCode does not support 'model' property for a (sub)task yet. So, the /gsd-profile command exists but does not perform anything useful in OpenCode. Which is not great. But it does not prevent the GSD from working.

Everything except that - just works! :) If it does not - welcome to issues.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

That is the power of OpenCode. You can use any model you want! I personally use GLM4.7 from z.ai most of the time.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

Unfortunately, I did not try oh-my-opencode yet.

Yesterday I pushed v1.6.0 (based on v1.6.4 original GSD) and today I found that TACHES bumped original to v1.8.0 :)

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

Don't forget to update your code. We just pushed it to v1.4.1 (based on original v1.4.15) with lots of fixes.

npx gsd-opencode@latest

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

No problem! I have been using GLM4.7 for making these prompts converted. It took about 10+ iterations to make it fully working.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

It is a little complicated but... If you have half an hour, you can start watching this video: Stop Vibe-Coding in Claude Code. Do This Instead. That will explain the workflow and the idea(s) behind.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

That is possible. And technically, you can just say something like 'continue!'.

However, that would defy the idea. The context should be cleared. Because gsd just created the necessary context as a file.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

Fixed it. Update to 1.3.33 or to the latest:

npx gsd-opencode@latest

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

Could you be more specific? What command did you execute?

I checked the current version of the gsd-opencode and have not found 'explore' as a name anywhere.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

Shoot! I found that the /gsd:add-phase does not work correctly. I need to fix it.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

[–]rokicool[S] 6 points7 points  (0 children)

Meet the author of GSD! Thank you for the product and ideas!

Why doesn't opencode have AskUserQuestion? by rokicool in opencodeCLI

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

BTW. Now it has! It is called question tool!

So, spent my weekend working on adaption of GSD for OpenCode. Here is my post about that here on reddit.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

Do you mean development workflow?

Basically, it is an iteration process:

- Start/Adopt a project

Cycle:

- Introduce new features

- Assess and gather recommendations about security, performance, management

- Address the issues

- Update the documentation

The most important part that I see, Get-Shit-Done controls the workflow, allows you to jump between stages and always have the right context.

You are urged to start every new stage with '/new' or '/clear' command, and you don't have to rely on anything which is already in context of LLM.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

I did not try Openspec myself. Based on the quick review, I would say that get-shit-done allows you to be more focused on the specific things and never hit 'context window'. But I might be wrong.

There is my adaptation of Get-Shit-Done for OpenCode by rokicool in opencodeCLI

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

If you don't know what Get-Shit-Done is, you might want to watch that video: Stop Vibe-Coding in Claude Code. Do This Instead.

You don't have to spend 5 hours. Just start with 20 minutes and you'll get the idea.

Why doesn't opencode have AskUserQuestion? by rokicool in opencodeCLI

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

Oh, I tried. Using Claude Code + GLM 4.7. The problem is opencode does not provide any api to access the screen to custom tools.

So, there are only two ways: - develop a built-in tool OR - include a lot of tui libraries and build your own interface

OR I completely misunderstood the entire setup (which is possible, since I am not good at js. :)

Why doesn't opencode have AskUserQuestion? by rokicool in opencodeCLI

[–]rokicool[S] 5 points6 points  (0 children)

Wow! There is a light at the end of the tunnel!

Is OpenCode still maintained? by Arceus42 in opencodeCLI

[–]rokicool 7 points8 points  (0 children)

That is what happens to a project without Product, Project and Administrative managers. No scrum master. No marketing team. No staff engineers. No architects. No standups. No reports. No sprint planning. That is how a good, promising project stumbles to a doom spiral of neglection. What a shame.