“Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA” — the project's own words, on GitHub
What it does
gstack turns Claude Code into a small engineering team with defined roles — a CEO for direction, an engineer, a designer, a QA lead, a security reviewer and a release engineer — each one a slash command with its own review gate. Instead of one long chat where Claude both writes and marks its own homework, you move a build through separate steps: plan it, build it, have a different role review it, test it, then ship it. It is built for someone already shipping a real software product with Claude Code who wants those checks to happen automatically instead of remembering to ask for them.
Replaces
an early engineering team's planning-and-review process
For
A solo builder or small team already shipping a real software product with Claude Code who wants CEO, design, QA and security review built into the workflow.
Not for
Not for a marketer or non-technical founder with no codebase — it's an engineering discipline layered on top of Claude Code, not a content or campaign tool.
Setup
15 min · Claude Code, Kimi, Gemini CLI or Codex · Claude Code, git, Bun v1.0+ (Node.js too, on Windows)
Get it running
Paste this into the AI that runs on your computer. It does the install, checks it works, and tells you what to type first. If anything fails, paste the error back to it.
Haven't got one of these running yet? The Kit sets one up on your computer — a guided install your assistant does for you, and five workflows to start with. 12 min to read, 15 min to set up
Paste into Claude Code
Install gstack (https://github.com/garrytan/gstack) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Claude Code, running on my machine.
1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password.
2. Clone https://github.com/garrytan/gstack into ~/tools/gstack and follow the README's install exactly.
3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says.
Tool-specific notes: Install with `git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup`.
It needs Bun v1.0+ on the machine (add Node.js too if the reader is on Windows).
Add the gstack section the setup script prints to the project's CLAUDE.md, so Claude Code knows the new slash commands exist.
Verify it loaded by running `/office-hours` inside Claude Code — if a CEO-style review responds, the skills are live.
If the Chromium or Playwright download hangs, set `GSTACK_SKIP_PLAYWRIGHT=1` first and skip it.
Leave telemetry off (it's off by default) unless the reader explicitly opts in.
4. Run the smallest test the README gives, and show me the output.
5. When it works, tell me what to type first, in one line, for this job: Run office hours on your idea.
If anything fails, show me the exact error and fix it before going on.
Paste into Kimi
Install gstack (https://github.com/garrytan/gstack) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Kimi, running on my machine.
1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password.
2. Clone https://github.com/garrytan/gstack into ~/tools/gstack and follow the README's install exactly.
3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says.
Tool-specific notes: Install with `git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup`.
It needs Bun v1.0+ on the machine (add Node.js too if the reader is on Windows).
Add the gstack section the setup script prints to the project's CLAUDE.md, so Claude Code knows the new slash commands exist.
Verify it loaded by running `/office-hours` inside Claude Code — if a CEO-style review responds, the skills are live.
If the Chromium or Playwright download hangs, set `GSTACK_SKIP_PLAYWRIGHT=1` first and skip it.
Leave telemetry off (it's off by default) unless the reader explicitly opts in.
4. Run the smallest test the README gives, and show me the output.
5. When it works, tell me what to type first, in one line, for this job: Run office hours on your idea.
If anything fails, show me the exact error and fix it before going on.
Paste into Gemini CLI
Install gstack (https://github.com/garrytan/gstack) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Gemini CLI, running on my machine.
1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password.
2. Clone https://github.com/garrytan/gstack into ~/tools/gstack and follow the README's install exactly.
3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says.
Tool-specific notes: Install with `git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup`.
It needs Bun v1.0+ on the machine (add Node.js too if the reader is on Windows).
Add the gstack section the setup script prints to the project's CLAUDE.md, so Claude Code knows the new slash commands exist.
Verify it loaded by running `/office-hours` inside Claude Code — if a CEO-style review responds, the skills are live.
If the Chromium or Playwright download hangs, set `GSTACK_SKIP_PLAYWRIGHT=1` first and skip it.
Leave telemetry off (it's off by default) unless the reader explicitly opts in.
4. Run the smallest test the README gives, and show me the output.
5. When it works, tell me what to type first, in one line, for this job: Run office hours on your idea.
If anything fails, show me the exact error and fix it before going on.
Paste into Codex
Install gstack (https://github.com/garrytan/gstack) on this computer and get it working for me. I am not a developer; explain each step in one line as you go and never skip one. You are Codex, running on my machine.
1. Check what this machine already has (git, Python or Node as the project needs, Docker if the README says so). Tell me anything missing and install it, asking me before anything that needs my password.
2. Clone https://github.com/garrytan/gstack into ~/tools/gstack and follow the README's install exactly.
3. Configure it. If it needs an API key or a login, stop and ask me for it; never guess one and never store it anywhere except where the README says.
Tool-specific notes: Install with `git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup`.
It needs Bun v1.0+ on the machine (add Node.js too if the reader is on Windows).
Add the gstack section the setup script prints to the project's CLAUDE.md, so Claude Code knows the new slash commands exist.
Verify it loaded by running `/office-hours` inside Claude Code — if a CEO-style review responds, the skills are live.
If the Chromium or Playwright download hangs, set `GSTACK_SKIP_PLAYWRIGHT=1` first and skip it.
Leave telemetry off (it's off by default) unless the reader explicitly opts in.
4. Run the smallest test the README gives, and show me the output.
5. When it works, tell me what to type first, in one line, for this job: Run office hours on your idea.
If anything fails, show me the exact error and fix it before going on.
What to point it at first
1
Run office hours on your idea
Start with the office-hours command on a real feature you're about to build — good output is the CEO role pushing back with questions before any code gets written.
2
Take one feature through the full sprint
Run the plan, build, review and QA commands on one small feature end to end, so you see every gate fire once before trusting it on something bigger.
3
Ship with the release gate on
Use the ship command for the first real release and read what it flags before it goes out — check that the security and QA steps actually ran, not just that the command finished.
What it must never do unattended
It drafts. It never posts.
Never let it invent a number, a customer or a quote.
Never let the ship command push to production or merge a change without you reading what it flagged first.
Who made it
garrytan/gstack on GitHub, under the MIT licence. 132,172 stars, checked 9 September 2026. Last change 6 September 2026. We did not write it; we checked it, and wrote this page so you can use it.