ORLOV GAMES

Skills ·

gstack — Garry Tan's Claude Code setup

Most people use a coding helper as one assistant. gstack is Garry Tan's setup. It treats that helper like a small team.

See gstack on GitHub

A skill is a pack of instructions you add to a coding tool.

gstack is free. You can read the code and use it. Garry Tan made it. He is the president and CEO of Y Combinator.

The project page calls it his Claude Code setup. It has 23 tools. They do six jobs: boss, designer, engineering lead, release lead, docs, and tester.

On 16 October 2026 it had 136,673 stars and 20,279 copies. The license is MIT. The code is TypeScript. The last update was that same day.

Six simple people marks around a round table.
One helper. Six jobs.

The six jobs

The project page names six jobs. The longer list in the README has more commands than the line that says "23 tools". These cards are the jobs, not every command.

The order of work

The README says the steps run in order. Each step reads what the one before it wrote.

The command /office-hours writes a short note. The planning step reads that note. The command /plan-eng-review writes a test plan. The command /qa reads that plan.

  1. Think. Six questions, then a short note.
  2. Plan. The boss, the designer, and the engineer look, in that order.
  3. Build. The plan becomes the change.
  4. Review. Find bugs the automatic tests miss, and check security.
  5. Test. Try the real behavior, and keep a test that fails.
  6. Ship. Run the checks, send the code, and open a pull request.
  7. Reflect. Look back once a week, and keep the notes the tool saved.
Think, then plan, build, review, test, ship, and look back. The full command list is in the project.

Commands along the way: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /autoplan, /review, /cso, /design-review, /qa, /qa-only, /ship, /land-and-deploy, /document-release, /retro, and /learn.

Other tools give a second opinion (/codex), help you stay safe (/careful, /freeze, /guard), and update the setup (/gstack-upgrade). To remove it, run ~/.claude/skills/gstack/bin/gstack-uninstall.

Who it is for

The README names three kinds of people.

Founders and CEOs who still ship their own work. People new to Claude Code who want jobs to pick, not an empty box. Tech leads who want a review, a test, and a release check on every change.

How to install

You need Claude Code, Git, and Bun 1.4.2 or newer. Setup will not run if Bun is older than 1.3.3. You need Node.js only on Windows.

The usual install is for Claude Code. ./setup --host auto sets it up for the other tools the README lists.

git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack
cd ~/.claude/skills/gstack && ./setup

Try /office-hours first. Then /plan-ceo-review, /review, and /qa.

A team install is optional. From the gstack folder, run ./setup --team. Then run gstack-team-init required. Then commit the .claude/ folder and CLAUDE.md. Use optional instead of required if you do not want to block your teammates.

See gstack on GitHub