Skip to content

gstack (Garry Tan)

github.com/garrytan/gstack · 71K stars (Apr 2026)

A Claude Code skill pack from Garry Tan (YC president). 23 specialised slash commands cover the full SDLC: /office-hours, /plan-ceo-review, /plan-eng-review, /design-review, /review, /qa, /ship, /cso, etc. Each command activates a focused “specialist” persona within a single Claude Code chat session.

  1. Role focus — each specialist has its own constraints and slice of the problem.
  2. Data flow control — what information passes between roles is governed.
  3. Quality gates — handoff points enforce standards.
  4. Boil the lake — each role finishes what it can do perfectly and skips what it can’t.
  5. Simplicity — push back against unnecessary complexity.
  • Boil the lake principle. Borrowed verbatim. Added to the prompts of the 5 roles most prone to sprawl: debugger, ui-qa, curator, product, architect.
  • Plan-review structure. The spirit of /plan-ceo-review (challenge the planner before any work) became our plan-reviewer role — but autonomous, gating, and integrated into the loop.
  • Slash-command-driven skill pack model. gstack lives inside a Claude Code chat session. A human invokes /qa when they’re ready. Our harness fires the equivalent autonomously.
  • 23 commands. Most of gstack’s commands are setup/installation/config (/connect-chrome, /setup-deploy, /setup-gbrain, /learn, /freeze, /unfreeze, /gstack-upgrade). We don’t need these.
  • /qa via real Playwright. We do real-browser QA via verdict (lighter-weight CLI) instead.
gstackPapercup
Human invokes specialistsOrchestrator invokes roles
Single Claude Code sessionPer-role fresh context (subprocess)
Skills auto-trigger on Claude’s reasoningRoles trigger on orchestrator decision verbs
23 commands13 roles
Cross-team setup (“team mode”)Per-mission isolation

gstack is excellent for what it is — a solo founder’s leverage tool inside Claude Code. The principles transfer beautifully to an autonomous loop, but the runtime model doesn’t. We took the principles, not the code.

Garry’s writeup explains the design.