Gary Tan is the CEO of Y Combinator.
He just open sourced his AI engineering team, all 23 of them. The part that makes it work isn't the code.
The repo is Gary Tan slash g stack.
100,000
stars in under two months. And here's the unusual part. Repos this opinionated normally split the room. This one isn't splitting.
So what did Tan ship that everyone's agreeing on? G Stack is 23 opinionated slash commands.
Not prompts, not configs,
roles.
There's a CEO,
a designer, an engineering manager, a release manager,
a doc engineer, and QA.
Each one is a command you type. They run inside Claude code plus nine other coding agents.
The skill layer is portable. The pitch is simple. An org chart compressed into a terminal.
And the most important command in it is the one nobody writes first. Most agent setups start the same way. You describe what you want. The model writes code.
GStack does something different.
The first command isn't slash build. It's slash office hours.
Before any line of code, an AI playing the CEO asks you six forcing questions about scope, about users, about trade offs. You have to answer them on the record. Only then does engineering get to start. Then the loop kicks in. Think, plan, build,
review,
test,
ship,
reflect.
Each phase has its own command.
The output of one is the input to the next, so handoffs don't get skipped.
Palumi's write up summed it up in three words.
Process beats prompts.
And one command, slash auto plan, chains the entire review pipeline together.
Type once. Get four roles reviewing in sequence. Let's open them. Look at the planning commands,
Slash plan CEO review challenges your scope with four decision modes. What to cut, what to defer, what to commit to.
Slash plan and review locks the architecture
with data flow diagrams and edge cases listed out.
And slash plan design review actually rates dimensions of your design on a zero to 10 scale.
It's the kind of pushback you'd normally only get from a real team. That covers the planning side. The building side has its own commands. Slash review runs a staff engineer code audit and auto fixes the obvious stuff.
Slash QA drives a real browser, finds bugs,
writes regression tests,
slash ship syncs main,
runs tests,
audits coverage,
pushes,
opens the PR.
One command,
full release.
There's even a slash CSO that does OWASP and stride threat modeling,
security review as a slash command.
So does any of this actually make him faster?
Tan says yes.
11,400
logical lines of code a day versus 14 back in 2013.
810
times.
He also says he runs 10 to 15 sprints in parallel.
The caveat, he uses logical LOC,
not raw.
Because in his words, AI inflates raw.
Whether you buy that math is your call, the repo doesn't depend on it. Critics aren't quiet.
Would the same repo from an unknown developer hit a 100,000 stars?
Probably not.
YC's platform amplifies everything tan ships,
and opinionation cuts both ways.
If your workflow matches TANs,
g stack is a gift.
If it doesn't, you'll fight the framework.
The augment code review put it well.
Study the repo before you install it. Still, Gstack is the operational version of a vibe a lot of senior engineers have been quietly admitting.
Andre Carpathi said it out loud.
Quote,
I don't think I've typed like a line of code probably since December,
unquote.
Gstack is what that sentence looks like when you write it down as code. And the meta punchline.
Open the Gstack commit log.
434
commits,
roughly 10 human contributors,
and 89 distinct coauthors,
almost all of them clawed
across basically every model version Anthropic released this year. The repo that teaches you how to ship with AI was itself shipped by AI.
Most honest dogfooding you'll see this year, fork it, steal three ideas,
or laugh at the LOC math. Just don't ignore. An org chart is now a slash command.