gstack turns Claude Code from one generic assistant into a team of specialists you can summon on demand. Six opinionated workflow skills for Claude Code. Plan review, code review, one-command shipping, browser automation, and engineering retrospectives — all as slash commands.
The slash command approach resonates with how we've been running Claude Code autonomously. We built 100+ SKILL.md files over 108 hours of unattended operation and the key insight was exactly this: specialized roles outperform a single generic agent. The biggest win was separating "plan review" from "code review" — when Claude tries to do both in one pass, it either rubber-stamps or gets lost in details. Question for the team: does GStack handle context window pressure when running multiple skills in sequence? That's been our main scaling challenge.
Why is this on Product Hunt? This is a bunch of prompts. You have got to be kidding.
Cool to see you launching this! Very useful too - I've already pulled in a few of these for my setup.
"Planning is not review. Review is not shipping. Founder taste is not engineering rigor. If you blur all of that together, you usually get a mediocre blend of all four."
I resonate with this so hard. Agents (like humans) can't perform as well when they wear too many hats. The future is coordinating teams of specialized agents like this with just the right amount of human in the loop.
That means you can have one session running /qa on staging, another doing /review on a PR, a third implementing a feature, and seven more working on other branches. All at the same time.
It's a freeing feeling when your workflows reach this level of parallelization. The productivity gains are insane.
Can't wait to try these out in Birdhouse. Thanks for sharing!
Nice to see Gary get the founder spotlight again. The amount of products he’s hunted and helped push to #1 is crazy.
I’ll be giving this stack a try! Congrats on the launch.
I've been using Claude Code for months and my setup is held together with scattered markdown files and random CLAUDE.md instructions. The idea of a curated, tested configuration from someone who actually pushes it hard is appealing. My main question: how opinionated is this? Half the value of Claude Code is customizing it to your specific codebase. If this overwrites my existing CLAUDE.md and memory files, that's a dealbreaker. Does it layer on top of existing config or replace it?
the slash command approach is really smart. I've been using Claude Code for a while and the biggest friction is always starting from scratch with context every time. having pre-built workflows for common tasks like code review and shipping saves so much time. curious if you're planning to add custom skill creation so teams can build their own workflows too?
Splitting Claude Code into role-specific slash commands like plan review, code review, and shipping is a practical pattern — it enforces structure that most developers skip when using a single generic agent. How opinionated are the workflow skills under the hood — are they rigid step-by-step procedures, or do they adapt based on the codebase context and project size?
Love seeing developer environment setups shared like this.
Is this mainly optimized for Claude Code workflows or does it also work well with Cursor / other AI coding tools?
I've been using Claude Code with MCP for about a year now and keep iterating on my setup. Curious what's in Garry's stack — is it mostly about the MCP server configuration or also specific prompt engineering patterns? The biggest unlock for me was getting file system + browser MCP tools working together. Does GStack cover the agentic workflow side or is it primarily IDE-focused?
The slash command approach resonates with how we've been running Claude Code autonomously. We built 100+ SKILL.md files over 108 hours of unattended operation and the key insight was exactly this: specialized roles outperform a single generic agent. The biggest win was separating "plan review" from "code review" — when Claude tries to do both in one pass, it either rubber-stamps or gets lost in details. Question for the team: does GStack handle context window pressure when running multiple skills in sequence? That's been our main scaling challenge.