claudekit / tools / gstack
[ Plugin · Development ]

gstack

Garry Tan's (YC CEO) exact Claude Code setup, packaged as slash commands. Call up roles like CEO, Designer, Eng Manager, QA, and Release Manager in sequence so a solo builder can work like a team.

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

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-hours interrogates whether the feature is really needed
  • Multi-perspective planning (Plan) — /plan-ceo-review, /plan-eng-review, /plan-design-review review 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) — /qa opens 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 — /retro for 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 — /qa launches 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 --host flag

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 with gstack-analytics.
  • Not on claude.com/plugins — installed directly via git clone.
§ 6

See also

same category · curated
[01]
[MCP] ARTEMIS · ARTEMIS turns natural-language instructions into reliable Android automation. Its native MCP server lets Claude Code drive real devices and emulators, run test workflows, and collect screenshots and Logcat output, while ARTEMIS's own agent performs the on-device steps in the background.
tool · claudekit.io / tools / artemis
[02]
[Tool] Claude Quickstarts · A collection of projects designed to help developers quickly get started with building deployable applications using the Claude API. Runnable quickstarts cover a customer support agent, a financial data analyst, computer use, browser automation, and Claude Managed Agents apps for Slack, Linear, Sentry, and MCP. Some quickstarts let Claude Code drive the setup.
tool · claudekit.io / tools / claude-quickstarts
[03]
[Tool] Worktrunk · A CLI for git worktree management, designed for running AI agents in parallel. Worktrees are addressed by branch name, and `wt switch -c -x claude feat` creates a worktree and starts Claude Code in it. The Claude Code plugin adds activity tracking in `wt list` and routes the worktrees agents create through Worktrunk.
tool · claudekit.io / tools / worktrunk
§ 7

Frequently Asked Questions

frequently asked
§ 7.1
What is gstack?
Y Combinator CEO Garry Tan's exact Claude Code setup, released as a collection of slash commands. It packages 23 roles — CEO, Designer, Eng Manager, QA, Release Manager, and more — that you call in sequence, so a solo builder moves through the same stages a team would.
§ 7.2
Where does it work?
It works in Claude Code, and with the `--host` flag in other coding agents like Cursor, OpenAI Codex CLI, and Factory Droid. It needs Bun v1.0+ and supports macOS, Linux, and Windows.
§ 7.3
How do I install it?
In Claude Code, paste `git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup`, then update your project's `CLAUDE.md` to reference the gstack skills.
§ 7.4
What about telemetry?
It's opt-in — gstack asks permission on first run. Even when enabled, it sends only the skill name, duration, success/fail status, gstack version, and OS. It never sends code, file paths, repo names, prompts, or user content, and you can disable it with `gstack-config set telemetry off`.
§ 7.5
Is it free?
Yes. It's open-source under the MIT license, with no premium tier and no waitlist.