Garry Tan’s (Y Combinator CEO) Claude Code setup (
garrytan/gstack).
Why it matters
Normally you prompt Claude Code from a blank screen, improvising each request. gstack instead gives you a set of slash commands with predefined procedures for each stage. One person makes a request and the planning, design, build, review, QA, and ship roles hand work to each other — so a solo builder can follow the flow a team would.
What you can do
gstack packages a Think → Plan → Build → Review → Test → Ship → Reflect sprint into slash commands. Representative commands per stage:
- Validate the product (Think) —
/office-hoursinterrogates whether the feature is really needed - Multi-perspective planning (Plan) —
/plan-ceo-review,/plan-eng-review,/plan-design-reviewreview scope from product, engineering, and design angles - Code and design review (Review) —
/review(staff-engineer audit),/design-review(a designer’s eye) - Real-browser QA (Test) —
/qaopens a real Chromium via Playwright, tests user flows, finds bugs, fixes them with atomic commits, and generates regression tests - Ship (Ship) —
/ship(sync, test, coverage audit, PR),/land-and-deploy(merge and verify production) - Reflect —
/retrofor a weekly retrospective
For example, on a new feature you go from /office-hours to narrow scope → plan review → build → /review → /qa for real browser testing → /ship for the PR, all in one flow.
Key features
- 23 role slash commands — organized by sprint stage from planning to ship and retro
- Real-browser QA —
/qalaunches Chromium to click-test flows, fix bugs, and generate regression tests automatically - Multi-perspective review — CEO, engineering, design, and developer-experience (DevEx) views, before and after the work
- Multi-agent support — beyond Claude Code, runs in Cursor, Codex, and others via the
--hostflag
Getting started
Global install:
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup
After installing, update your project’s CLAUDE.md to reference the gstack skills. To apply it across a shared repo for the whole team, use ./setup --team.
Notes
- Requirements — Bun v1.0+ (primary runtime), Git, Claude Code. Supports macOS, Linux, and Windows 11 (Node.js fallback for Playwright on Windows)
- License — MIT, no premium tier or waitlist
- Telemetry — opt-in; gstack asks on first run. Even when enabled it sends only the skill name, duration, success/fail status, gstack version, and OS — never code, file paths, repo names, or prompts. Disable with
gstack-config set telemetry off; view local analytics withgstack-analytics. - Not on claude.com/plugins — installed directly via git clone.