After a 4 year long hiatus, today I came back to my blog (and also released an OSS tool, what a day).
Here's my newest blog post: A GSD System for Claude Code
https://estebantorr.es/blog/2026/2026-02-03-a-gsd-system-for-claude-code/
The OSS tool is linked in the blog but I'll leave it here as well: https://github.com/esttorhe/blogwatcher-ui
@esttorhe supports This supports my experience with GSD.
The tool is good but eats truck loads of tokens. Then again, do you have truck loads of time, I don't, so I use GSD.
I can easily generate complex systems with Claude Pro only to hit 5 h limit. Then I can spend a lot of time reviewing and verofying what was made before proceeding to the next research plannong step.
I still wonder is how to empower a team of developers doing client work at this speed without risking quality.
@nemeciii yeah, same. Haven't had teams work with this approach.
Not suggesting a solution, but wondering if having a "product manager" (Claude account user) that generates the roadmap and plans and makes sure that the spec is up to requirements; and then they pass it down to an engineer (another Claude account) that will execute on the plan and validate the execution would be a feasible approach to get fast deliveries and maintaining quality
@esttorhe dividing work by separate parts of the system might also work.
For example this human developer works on reporter features, the other with client side features another with external integrations...
A fully event sourced CQRS system might be a good fit. Features depending on existing projections are quite separate and easily extendable in comparison of a sprawling monolithic application.
Esteban Torres
Matti Järvinen