How One YC CEO Turned Claude Code Into a Full Engineering Team

Garry Tan’s GStack has gone completely viral, and for good reason.
The YC CEO open-sourced his personal toolkit, and it's the ultimate cheat code for devs.
It turns Claude Code from a basic chatbot into an entire virtual engineering department.
Instead of basic prompts, you summon specialized AI "brains" on demand.
Tens of thousands are already using it.
→ The Visionary:
/plan-ceo-review acts like Brian Chesky. It stops you from building boring features and pushes for magic.
→ The Architect:
/plan-eng-review draws sequence diagrams and state machines before coding.
→ The Paranoid Reviewer:
/review looks for N+1 queries and stale reads.
→ The QA Lead:
/qa literally logs into your staging environment, clicks around, takes screenshots, and gives your app a health score in 60 seconds.
The QA tool alone is built on Bun and Playwright, running 20x faster than Claude’s native Chrome MCP with zero context bloat.
He used this exact setup to ship 100 PRs a week for the last 50 days.
100% free and open-source.
Here's the repo → https://lnkd.in/eX9sge3Q

• GStack is real and did go viral. Garry Tan released gstack, an open-source Claude Code system for planning, code review, QA, and shipping. Garry Tan open-sourced his personal Claude Code configuration as gstack, and it crossed 108K GitHub stars and 16.1K forks within weeks. MarkTechPostAugment Code
• The "virtual engineering team" framing is accurate — the repo packages opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA roles, all running as slash commands inside Claude Code and other AI coding agents. Augment Code
• Plan/review/QA slash commands are real, including core commands like /plan-ceo-review, /plan-eng-review, /ship, and /retro. Dev|Journal
• The persistent browser/QA subsystem is real and technically as described — gstack runs a long-lived headless Chromium daemon communicating over localhost HTTP, with cold starts around 3–5 seconds and subsequent calls running in roughly 100–200ms, and is built on Bun to use native SQLite access for reading Chromium cookie databases. MarkTechPostDev|Journal

Imprecise or unverifiable:

• Command names differ from official ones in some sources — I found real commands like /plan-eng-review, /ship, /retro, but couldn't independently confirm /review and /qa as the exact command names (they may exist under slightly different names, or the tool has been updated — the skill count itself changed across sources from 8 → 23 → 31 as the project evolved rapidly).
• "20x faster than Claude's native Chrome MCP" — the underlying latency improvement (3-5 sec → ~100-200ms via persistent daemon) is real and roughly consistent with a 20x-plus speedup, so this figure is plausible, though I couldn't find it stated as an exact official benchmark.
• "100 PRs a week for 50 days" — I couldn't verify this specific productivity figure. A related, differently-sourced claim mentions Tan shipping 600,000+ lines of production code over 60 days of part-time use — a similar but not identical stat, suggesting the post may be citing a rounded or slightly different version of Tan's real reported numbers. Codex Knowledge Base