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.
Free
Launch Team
Render: Get up to $100K in startup creditsThe fastest way to launch and scale your startup in the cloud
Promoted
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?
we arrived at the same pattern independently building health data infrastructure. curious how /browse handles auth behind enterprise tenant boundaries, we test clinical platforms behind NHS and pharma logins.
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?
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?
Really impressed by the slash command architecture. Treating these as specialized teammates you can summon instantly is exactly right. The separation of plan review from code review catches problems early. How do you handle priority when multiple skills could apply?
This is amazing, Garry!
I am curious how you use it. do you usually run things sequentially, or is it parallel most of the time? And in the parallel case, how do you keep the flow in sync when each sub-agent is continuously making changes- do you use git worktree?
The role specialization concept makes a lot of sense - having Claude switch between 'plan reviewer' and 'code reviewer' modes enforces the mental discipline most developers skip when using generic assistants. What's interesting is how this mirrors how effective engineering teams actually work: distinct review stages with different objectives.
Do the slash commands maintain any state between invocations? For instance, does /code-review remember issues flagged in a prior /plan-review session on the same feature?