gstack: Garry Tan's Claude Code role-play kit for solo shipping

What gstack actually is

gstack is a collection of 23 slash commands for Claude Code, published by Garry Tan, the president and CEO of Y Combinator. The commands are meant to replace a blank prompt with structured roles: a CEO that rethinks the product, an engineering manager that locks architecture, a designer that catches what Tan calls AI slop, a reviewer that finds production bugs, a QA lead that opens a real browser, a security officer that runs OWASP and STRIDE audits, and a release engineer that ships the pull request. The README describes the slash commands as all Markdown, all free, MIT license. The target user is a technical founder or a staff engineer who wants a repeatable process for shipping without a human team. The README is explicit about who it is for: founders, first-time Claude Code users, and tech leads who want rigorous review on every PR.

The mechanism: slash commands as a virtual team

The core idea is that each slash command encodes a workflow. You invoke /office-hours to describe what you are building, then /review on a branch, then /qa on a staging URL. The commands are not standalone programs; they are Markdown instructions that Claude Code interprets. The README gives a quick start sequence: install, run /office-hours, run /review, run /qa, and stop there to decide if the tool fits. The design assumes that Claude Code can follow long, structured prompts reliably. The commands are opinionated, meaning they enforce Tan's specific standards for what a CEO review or a QA pass should include. That is both the strength and the risk: you get a process that works for one person, but you inherit their biases.

Installation and team mode

Installation is a prompt that you paste into Claude Code, which tells it to run: git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup. The same prompt then tells Claude to add a gstack section to CLAUDE.md, with no skill list, that instructs Claude Code to use the /browse skill for all web browsing, never the mcp__claude-in-chrome__* tools. There is a team mode for shared repos: you run ./setup --team from inside your repo, then bin/gstack-team-init required, and commit the .claude/ and CLAUDE.md changes. The README claims this gives auto-update checks throttled to once per hour, network-failure-safe, and silent. You can swap required for optional to nudge teammates instead of blocking them. The team mode avoids vendored files and version drift, but it also means every teammate's Claude Code session checks for updates automatically and follows the stable channel (the twice-weekly tagged release) unless someone sets update_channel to main, which could change a workflow without a manual upgrade.

OpenClaw integration and native skills

gstack also runs on agents other than Claude Code. A bare ./setup installs for Claude Code only; run inside OpenClaw, Hermes or a Dot, it also registers gstack's skills with that harness (see docs/hosts.md). You can pick another agent with --host <name>, or install for every agent setup detects with --host auto. In the README's table, Claude Code is the full tier and the other hosts shown, including Codex CLI, OpenCode, Cursor, Factory Droid, Kiro and GitHub Copilot CLI, are experimental.

The productivity claims and the LOC controversy

The README says the story, the productivity numbers and how the author runs ten sprints at once are in docs/why-gstack.md. Those figures are the author's own and cannot be verified from the repository, so treat any productivity multiplier as self-reported. The value of gstack does not depend on them; it depends on whether the slash commands produce useful output.

Limitations and wrong-tool cases

The most obvious limitation is that gstack is only as good as Claude Code's ability to follow the Markdown instructions. If you use a different AI coding assistant, support is weaker: the README lists other hosts such as Codex CLI, OpenCode and Cursor as experimental, with safety skills advisory rather than enforced. The commands are also opinionated to Tan's workflow, so a CEO review or a design consultation will reflect his standards, not yours. You can fork and modify, but that is maintenance work. Another limitation is the team mode auto-update: it checks for updates at the start of every session (throttled to once an hour and silent), which could change your team's workflow without notice. By default team mode follows the stable channel, the twice-weekly tagged release; `gstack-config set update_channel main` follows every merge instead. If you need deterministic behavior for a regulated environment, this is the wrong tool. Also, the QA command opens a real browser, and the README recommends the Aside browser on macOS 15+, otherwise ./setup builds gstack's own bundled browser.

Alternatives and what to compare

The closest alternative is a plain Claude Code setup with your own CLAUDE.md and custom slash commands. The difference is that gstack gives you a pre-built, opinionated set of roles and workflows, while a custom setup requires you to write those prompts yourself. The real comparison is between adopting gstack's conventions and building your own prompt library. gstack saves you the initial writing effort but locks you into Tan's process. If you want to understand what each command does in detail, you need to read the Markdown files in the repository, which the README does not fully document.

Maintenance, license, and upgrade path

gstack is MIT licensed, so you can fork, modify, and redistribute it freely. The repository is not archived, its last push was on 2026-11-02, and it publishes frequent tagged releases (v1.92.55.0 on 2026-11-02, v1.91.318.0 on 2026-10-29, v1.91.242.0 on 2026-10-26). There is a /gstack-upgrade command, which implies that upgrading is a supported workflow. In team mode, the auto-update mechanism means you do not have to manually upgrade, but you also lose control over when changes arrive. The README says there are no vendored files in your repo, so the code lives in ~/.claude/skills/gstack on each machine. The README points to docs/uninstall.md for removing gstack. The maintenance cost is low if you accept the defaults, but if you customize the commands, you will need to merge upstream changes manually. The repository has a CHANGELOG.md and the README links docs/releases.md, so check those for breaking changes.

Editorial conclusion

Adopt gstack if you are a technical founder or solo developer who already lives inside Claude Code and wants structured prompts for planning, review, and QA. Skip it if you need first-class support outside Claude Code, since the other hosts the README lists (Codex CLI, OpenCode, Cursor and others) are experimental or if you expect it to replace human judgment in architecture or design. Before adopting, verify that the /review and /qa skills actually run against your stack, confirm that the auto-update behavior in team mode matches your repo's governance, and read docs/why-gstack.md to see where the productivity numbers come from. gstack is a personal workflow made public, not a product with a support contract, so treat its defaults as starting points to fork and modify.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. README
4. Releases