GSD Plugin packaging for Claude Code marketplace

[jnuyens]

Hi there,

I've created a Claude Code plugin packaging of GSD that's available as a marketplace plugin:

Repository: https://github.com/jnuyens/gsd-plugin

What it does

Repackages the GSD workflow system as a native Claude Code plugin with:

• Single-command install: claude plugin marketplace add jnuyens/gsd-plugin && claude plugin install gsd@gsd-plugin
• ~92% token overhead reduction — skills use context: fork isolation instead of loading via CLAUDE.md
• MCP server exposing project state as queryable resources and mutation tools
• Hooks for session-start context loading, workflow enforcement, and tool-use monitoring
• Cross-session memory via Claude Code's memdir system
• Auto-migration from legacy GSD installs (moves old files to -legacy/ backups)

Currently tracking upstream GSD 1.33.0.

Structure

.claude-plugin/
  plugin.json          # Plugin manifest with MCP server config
  marketplace.json     # Marketplace catalog entry
skills/                # All 60 /gsd:* slash commands
agents/                # 21 agent definitions
hooks/                 # Session start, pre/post tool use hooks
mcp/                   # MCP server (stdio JSON-RPC)
bin/                   # gsd-tools.cjs + lib/ (synced from upstream)
templates/             # Planning artifact templates
references/            # Reference docs for agents

Would upstream be interested?

A few options:

1. Integrate into upstream — ship the plugin layout as part of the official GSD distribution
2. Official blessing — keep it separate but reference it from GSD docs as the recommended Claude Code plugin install method
3. Stay independent — I'll keep syncing from upstream releases

Happy to discuss what makes sense. The plugin format is where Claude Code is heading for distribution, so having an official plugin packaging could make GSD more accessible.

Thanks for building GSD — it's a great workflow system.

— Jasper Nuyens

[trek-e]

Hi @jnuyens — thanks for building this and sharing it! This is great work.

However, this is a question ("Would upstream be interested?") rather than a feature request, so this isn't the right venue. For open-ended discussions like this, please use GitHub Discussions.

If after discussion there's interest in integrating plugin packaging into upstream GSD, follow up with a Feature Request that includes the full required spec (user stories, acceptance criteria, scope, maintenance burden, etc.).

In the meantime, the community will likely be interested in your plugin — worth posting in Discussions.