garrytan / gstack

gstack **gstack turns Claude Code from one generic assistant into a team of specialists you can summon on demand.** Eight opinionated workflow skills for Claude Code. Plan review, code review, one-command shipping, browser automation, QA testing, and engineering retrospectives — all as slash commands. Without gstack • The agent takes your request literally — it never asks if you're building the right thing • It will implement exactly what you said, even when the real product is something bigger • "Review my PR" gives inconsistent depth every time • "Ship this" turns into a long back-and-forth about what to do • The agent can write code but can't see your app — it's half blind • You still do QA by hand: open browser, click around, check pages, squint at layouts With gstack | Skill | Mode | What it does | |-------|------|--------------| | | Founder / CEO | Rethink the problem. Find the 10-star product hiding inside the request. | | | Eng manager / tech lead | Lock in architecture, data flow, diagrams, edge cases, and tests. | | | Paranoid staff engineer | Find the bugs that pass CI but blow up in production. Triages Greptile review comments. | | | Release engineer | Sync main, run tests, resolve Greptile reviews, push, open PR. For a ready branch, not for deciding what to build. | | | QA engineer | Give the agent eyes. It logs in, clicks through your app, takes screenshots, catches breakage. Full QA pass in 60 seconds. | | | QA lead | Systematic QA testing. On a feature branch, auto-analyzes your diff, identifies affected pages, and tests them. Also: full exploration, quick smoke test, regression mode. | | | Session manager | Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless session. Test authenticated pages without logging in manually. | | | Engineering manager | Team-aware retro: your deep-dive + per-person praise and growth opportunities for every contributor. | Demo: one feature, five modes I start almost every feature in plan mode. I describe what I want to build, then use to pressure-test whether I am even building the right thing. Only after the product direction is locked do I shift into engineering, review, ship, and test. Who this is for You already use Claude Code heavily and want consistent, high-rigor workflows instead of one mushy generic mode. You want to tell the model what kind of brain to use right now — founder taste, engineering rigor, paranoid review, or fast execution. This is not a prompt pack for beginners. It is an operating system for people who ship. How to fly: 10 sessions at once gstack is powerful with one Claude Code session. It is transformative with ten. Conductor runs multiple Claude Code sessions in parallel — each in its own isolated workspace. That means you can have one session running on staging, another doing on a PR, a third implementing a feature, and seven more working on other branches. All at the same time. Each workspace gets its own isolated browser instance automatically — separate Chromium process, cookies, tabs, and logs stored in inside each project root. No port collisions, no shared state, no configuration needed. and sessions never interfere with each other, even across ten parallel workspaces. This is the setup I use. One person, ten parallel agents, each with the right cognitive mode for its task. That is not incremental improvement. That is a different way of building software. Install **Requirements:** Claude Code, Git, Bun v1.0+. compiles a native binary — works on macOS and Linux (x64 and arm64). Step 1: Install on your machine Open Claude Code and paste this. Claude will do the rest. > Install gstack: run then add a "gstack" section to CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp\_\_claude-in-chrome\_\_\* tools, and lists the available skills: /plan-ceo-review, /plan-eng-review, /review, /ship, /browse, /qa, /setup-browser-cookies, /retro. Then ask the user if they also want to add gstack to the current project so teammates get it. Step 2: Add to your repo so teammates get it (optional) > Add gstack to this project: run then add a "gstack" section to this project's CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp\_\_claude-in-chrome\_\_\* tools, lists the available skills: /plan-ceo-review, /plan-eng-review, /review, /ship, /browse, /qa, /setup-browser-cookies, /retro, and tells Claude that if gstack skills aren't working, run to build the binary and register skills. Real files get committed to your repo (not a submodule), so just works. The binary and node\_modules are gitignored — teammates just need to run once to build (or handles it automatically on first use). What gets installed • Skill files (Markdown prompts) in (or for project installs) • Symlinks at , , , etc. pointing into the gstack directory • Browser binary at (~58MB, gitignored) • (gitignored) • saves JSON snapshots to in your project for trend tracking Everything lives inside . Nothing touches your PATH or runs in the background. --- --- How I use these skills Created by Garry Tan, President & CEO of Y Combinator. I built gstack because I do not want AI coding tools stuck in one mushy mode. Planning is not review. Review is not shipping. Founder taste is not engineering rigor. If you blur all of that together, you usually get a mediocre blend of all four. I want explicit gears. These skills let me tell the model what kind of brain I want right now. I can switch cognitive modes on demand — founder, eng manager, paranoid reviewer, release machine. That is the unlock. --- This is my **founder mode**. This is where I want the model to think with taste, ambition, user empathy, and a long time horizon. I do not want it taking the request literally. I want it asking a more important question first: **What is this product actually for?** I think of this as **Brian Chesky mode**. The point is not to impl…