Skip to main content
Back

YC's Garry Tan Open-Sources gstack, His 810x Productivity Claude Code Setup

Garry Tan open-sourced his Claude Code workflow as gstack, a free MIT-licensed pack of 23 role-based slash commands that runs a full sprint from idea to shipped PR.

Repo, Full Access
  • Garry Tan open-sourced gstack, his personal Claude Code setup with 23 role-based slash commands.
  • Skills chain into a full sprint: think, plan, build, review, test, ship, reflect.
  • Standout commands include /office-hours, /autoplan, /qa, /review, /cso, and /ship.
  • Works with 10 coding agents beyond Claude, including Codex CLI, Cursor, and OpenCode.
  • Ships prompt-injection defenses, egress receipts, and safety guardrails like /careful and /freeze.
  • MIT licensed and free with no premium tier or waitlist, install via a single git clone.

Y Combinator president Garry Tan just open-sourced the exact Claude Code setup he uses to ship features while running YC full time. It's called gstack, and instead of being another agent framework or MCP server, it's a pack of opinionated Markdown slash commands that turn Claude Code into something closer to a virtual engineering team than a copilot.

The pitch is aggressive. Tan claims that on logical code change, his 2026 run rate is roughly 810x his 2013 pace, and he's attributing the delta almost entirely to tooling. gstack is his answer to the question of how one person ships like twenty.

Slash commands as job titles

The repo ships twenty-three specialist skills and eight power tools, all as slash commands, all Markdown, all MIT licensed. Each command role-plays a specific job function. A few of the load-bearing ones:

  • /office-hours plays the YC partner. It pushes back on your framing with forcing questions and writes a design doc that downstream skills read.
  • /plan-ceo-review looks for the 10-star product hiding inside your feature request, with four scope modes from Expansion to Reduction.
  • /plan-eng-review acts as an eng manager that locks in architecture, ASCII data-flow diagrams, and edge cases before code gets written.
  • /review is the staff engineer that finds bugs that pass CI but blow up in production, and auto-fixes the obvious ones.
  • /qa opens a real Chromium browser, clicks through flows, fixes bugs it finds with atomic commits, and generates a regression test for each one.