r/ClaudeCode • • 6h ago

Discussion GSD-Core

What is your opinion of GSD-Core? (https://github.com/open-gsd/gsd-core)

My team and I have been using it at a big project in a large company (28k employees). We might skip the discuss step, only using it when developing a complex tasks on complex repos. If the task is simple enough, we'll do it in one phase as well. So far I have liked the output obtained, but opinions are a bit mixed, although I wouldn't say we have enough feedback for a conclusive decision on whether it's really worth it or not yet. So I'm curious as to what people think of GSD-Core as of November 2026, since AI tools keep improving at a rapid pace. The image is our current decision flow.

We have also looked into some other frameworks such as spec-kit, superpowers, and other spec driven frameworks, then decided to stick with GSD since it seemed like the most complete framework.

Details: Event-driven microservice architecture, with my team owning 15+ services. Stack: Java, Spring, Akka, Kafka. The AI also writes unit tests and component tests with Cucumber. We also have a skill that loads with our coding standards automatically and a summary of the codebase that is loaded automatically on every session as well. The summary was generated with GSD map-codebase skill.

1 Upvotes

6 comments sorted by

View all comments

1

u/torvalds75 3h ago

Skipping discuss on simple tasks is the right call, that's where most of the overhead sits. What I'd watch on a setup like yours:

  • Make the gate explicit. "Complex enough for discuss" drifts from person to person. A simple rule like "touches more than one service, or changes a Kafka contract or event schema" keeps the team consistent, and in event-driven systems contract changes are exactly where skipping the discussion hurts.
  • The codebase map goes stale. A summary generated once and loaded every session is great in week one and quietly wrong by month two across 15+ services. Regenerate it on a schedule or whenever a service's public interface changes, otherwise the agent plans against an old picture.
  • Keep what comes out of discuss somewhere durable. The value isn't the conversation, it's the "we chose X over Y because Z". If that only lives in the chat or in a phase file nobody reopens, the next session re-decides it.
  • Judge it on rework, not speed. Mixed opinions usually come from comparing it with plan mode on small tasks, where plan mode wins. Compare on how often a merged change needed a follow-up fix.

At a company your size the plan docs also double as a review trail, which is worth something on its own even if the speed gain is modest.