Bitwise AI · Youtube · 04:39

The YC CEO Open-Sourced His AI Engineering Team

How Garry Tan compressed a 23-person org chart into a terminal, and why the first command is not /build.

Posted
May 23rd 2026
today
Duration
04:39
Format
Tutorial
educational
Channel
BA
Bitwise AI
§ 01 · The Hook

The bait, then the rug-pull.

Garry Tan shipped a GitHub repo called gstack, 23 opinionated slash commands, 100K stars in 71 days, and the narrator immediately undercuts the obvious read: the part that makes it work is not the code. That is the hook. The rest of the video earns it.

§ · Chapters

Where the time goes.

00:00 – 00:13

01 · Cold open, credibility hook

Typing-hands B-roll. Garry Tan is YC CEO. GitHub card: 100K stars, 14.9K forks. Spoken undercut: it is not the code.

00:13 – 00:52

02 · 23 roles, not prompts

Animated org chart builds CEO to QA. Reframe: not prompts, not configs, roles. Portable skill layer across 10 agents.

00:52 – 01:08

03 · The command nobody writes first

Most agent setups: describe plus model writes code. GStack does something different. Sets up the /office-hours reveal.

01:08 – 01:52

04 · /office-hours and the 7-phase loop

Six forcing questions on scope, users, trade-offs, on the record. 7-phase wheel animates. /auto-plan chains the entire pipeline.

01:52 – 02:15

05 · Planning commands deep-dive

/plan-ceo-review, /plan-eng-review, /plan-design-review. Actual SKILL.md contents shown from GitHub.

02:15 – 02:51

06 · Building side commands

Terminal mockup: /review (staff audit, 12 fixes), /qa (browser-driven, 3 bugs), /ship (full release one command), /cso (OWASP + STRIDE).

02:51 – 03:21

07 · The 810x claim

Bar chart: 14 logical LOC/day in 2013 vs 11,400 in 2026. Caveat surfaced: logical not raw. 10-15 parallel sprints.

03:21 – 03:53

08 · Critics and caveats

@halo_check: YC amplifies. @opinionation: opinionation cuts both ways. Augment: study before installing.

03:53 – 04:39

09 · Meta-punchline

434 commits, 10 humans, 89 Claude co-authors across every Anthropic model. The repo teaching you to ship with AI was shipped by AI.

§ · Storyboard

Visual structure at a glance.

open, typing hands
hook open, typing hands 00:01
GitHub card, 100K
hook GitHub card, 100K 00:05
ROLES, org chart
promise ROLES, org chart 00:33
/office-hours reveal
value /office-hours reveal 01:05
PROCESS BEATS PROMPTS wheel
value PROCESS BEATS PROMPTS wheel 01:41
/ship terminal mockup
value /ship terminal mockup 02:35
810x bar chart
value 810x bar chart 02:58
critic tweets
value critic tweets 03:33
AN ORG CHART IS NOW A SLASH COMMAND
cta AN ORG CHART IS NOW A SLASH COMMAND 04:27
§ · Frameworks

Named ideas worth stealing.

01:26 model

The 7-Phase AI Dev Loop

  1. Think
  2. Plan
  3. Build
  4. Review
  5. Test
  6. Ship
  7. Reflect

GStack maps one slash command to each dev cycle phase. Output of one is input of the next, handoffs do not get skipped.

Steal for JoeFlow sessions panel, agent orchestration framing
00:29 concept

Org Chart as Slash Commands

23 roles compressed into terminal commands with SKILL.md files: CEO, designer, EM, release manager, doc engineer, QA.

Steal for JoeFlow orchestration framing, MCN+ agent team positioning
01:08 model

/office-hours, Forcing Questions Before Code

  1. Scope
  2. Users
  3. Trade-offs

Six CEO-mode forcing questions answered on the record before engineering begins. Prevents scope creep at the start.

Steal for Morning launch session framing in JoeFlow
01:40 concept

Process beats prompts

Structure (defined phases, roles, handoffs) outperforms clever prompts with no scaffolding.

Steal for Positioning JoeFlow as a process layer, not a prompt box
§ · Quotables

Lines you could clip.

01:40
"Process beats prompts."
Three words, zero setup needed. → TikTok hook
01:04
"The first command is not /build. It is /office-hours."
Flip structure, subverts expectation in one line. → IG reel cold open
03:57
"I have not typed a line of code probably since December."
Karpathy standalone mic-drop. → newsletter pull-quote
04:20
"The repo that teaches you how to ship with AI was itself shipped by AI."
Perfect closer, ironic, tidy, memorable. → IG reel cold open
04:39
"An org chart is now a slash command."
Title-card punchline. Zero context needed. → TikTok hook
§ · Pacing

How they spent the runtime.

Hook length13s
Info densityhigh
Filler2%
§ · Resources Mentioned

Things they pointed at.

00:10linkgarrytan/gstack ↗
01:39linkPulumi write-up on gstack
03:21linkAugment code review of gstack
§ · CTA Breakdown

How they asked for the click.

04:30 link
"Fork it, steal three ideas, or laugh at the LOC math. Just do not ignore. An org chart is now a slash command."

Soft fork CTA in the outro, no hard sell, no subscribe pitch. The CTA is the lesson itself.

§ 04 · The Script

Word for word.

HOOK opening / re-engagementCTA the pitch metaphor analogy story
00:00HOOKGary 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.
00:10HOOKThe repo is Gary Tan slash g stack. 100,000 stars in under two months.
00:16And here's the unusual part. Repos this opinionated normally split the room. This one isn't splitting.
00:23So what did Tan ship that everyone's agreeing on? G Stack is 23 opinionated slash commands. Not prompts, not configs,
00:32roles. There's a CEO, a designer, an engineering manager, a release manager,
00:38a doc engineer, and QA. Each one is a command you type. They run inside Claude code plus nine other coding agents.
00:46The skill layer is portable. The pitch is simple. An org chart compressed into a terminal.
00:52And the most important command in it is the one nobody writes first. Most agent setups start the same way. You describe what you want.
01:00The model writes code. GStack does something different. The first command isn't slash build.
01:06It'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.
01:19Only then does engineering get to start. Then the loop kicks in. Think, plan, build,
01:26review, test, ship,
01:28reflect. Each phase has its own command. The output of one is the input to the next, so handoffs don't get skipped.
01:37Palumi's write up summed it up in three words. Process beats prompts. And one command, slash auto plan, chains the entire review pipeline together.
01:47Type once. Get four roles reviewing in sequence. Let's open them.
01:51Look 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.
02:01Slash 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.
02:16It'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.
02:23Slash review runs a staff engineer code audit and auto fixes the obvious stuff. Slash QA drives a real browser, finds bugs, writes regression tests,
02:34slash ship syncs main, runs tests, audits coverage,
02:39pushes, opens the PR. One command,
02:42full release. There's even a slash CSO that does OWASP and stride threat modeling, security review as a slash command.
02:51So does any of this actually make him faster? Tan says yes. 11,400
02:57logical lines of code a day versus 14 back in 2013. 810 times.
03:05He also says he runs 10 to 15 sprints in parallel. The caveat, he uses logical LOC, not raw.
03:13Because 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.
03:21Would the same repo from an unknown developer hit a 100,000 stars? Probably not. YC's platform amplifies everything tan ships,
03:31and opinionation cuts both ways. If your workflow matches TANs, g stack is a gift.
03:38If it doesn't, you'll fight the framework. The augment code review put it well. Study the repo before you install it.
03:47Still, Gstack is the operational version of a vibe a lot of senior engineers have been quietly admitting. Andre Carpathi said it out loud. Quote,
03:57I 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.
04:06And the meta punchline. Open the Gstack commit log. 434
04:12commits, roughly 10 human contributors, and 89 distinct coauthors,
04:18almost 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.
04:28CTAMost honest dogfooding you'll see this year, fork it, steal three ideas, or laugh at the LOC math. Just don't ignore.
04:36CTAAn org chart is now a slash command.
— full transcript
§ 05 · For Joe

Steal the format, then steal the framework.

Killing Excuses playbook

The most powerful thing in gstack is not any single slash command, it is that the whole org is portable.

  • Lead with a credibility number that stops the scroll (100K stars, 71 days), then immediately undercut the obvious read.
  • The /office-hours pattern is directly usable in JoeFlow: before spinning up agents, force six scope/user/trade-off questions on the record.
  • Process beats prompts is a positioning unlock. JoeFlow is not a transcription box, it is a process layer that compresses your morning workflow into a terminal.
  • Bitwise editorial format (title card + mechanism + proof + critic + meta-twist) turns a trending repo into a 5-minute course. Replicable for any tool breakdown.
  • The meta-punchline structure (the thing that teaches X was itself built with X) is a content template: The productivity app was built using the system it teaches.
§ 05 · For You

What gstack actually means if you build with Claude Code.

If you are building with AI agents

Before you write a line of code, an AI should challenge your scope and you should have to answer on the record.

  • Fork garrytan/gstack and read /office-hours first. Six questions before engineering starts is the discipline most solo builders skip.
  • The 7-phase loop works as a checklist even without the slash commands. Just do not skip handoffs.
  • /plan-design-review rates design 0-10 across multiple dimensions. Run it before committing to architecture.
  • 10-15 parallel sprints is a different mode of working, not just a faster version of the old mode.
  • If your workflow does not match Tan's, study the SKILL.md files before installing any of it.
§ 06 · Frame Gallery

Visual moments.

02:2102:21