Modern Creator
Bitwise AI · YouTube

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
yesterday
Duration
Format
Tutorial
educational
Views
2.5K
94 likes
Members feature

Chat with this breakdown.

Modern Creator members can chat with any breakdown — ask for the hook, quote a framework, find the exact transcript moment. Unlocks at T2: refer 3 friends + add your own API key.

Create a free account →
Chapters

Where the time goes.

00:0000: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:1300: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:5201: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:0801: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:5202:15

05 · Planning commands deep-dive

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

02:1502: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:5103: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:2103:53

08 · Critics and caveats

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

03:5304: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.

Takeaway

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.
Resources Mentioned

Things they pointed at.

01:39linkPulumi write-up on gstack
03:21linkAugment code review of gstack
Quotables

Lines you could clip.

01:40
Process beats prompts.
Three words, zero setup needed.TikTok hook↗ Tweet quote
01:04
The first command is not /build. It is /office-hours.
Flip structure, subverts expectation in one line.IG reel cold open↗ Tweet quote
03:57
I have not typed a line of code probably since December.
Karpathy standalone mic-drop.newsletter pull-quote↗ Tweet 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↗ Tweet quote
04:39
An org chart is now a slash command.
Title-card punchline. Zero context needed.TikTok hook↗ Tweet quote
The Script

Word for word.

metaphoranalogystory
00:00Gary 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:10The 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, roles.
00:33There's a CEO, a designer, an engineering manager, a release manager, a doc engineer, and QA.
00:40Each one is a command you type. They run inside Claude code plus nine other coding agents. The skill layer is portable.
00:48The pitch is simple. An org chart compressed into a terminal. And the most important command in it is the one nobody writes first.
00:56Most agent setups start the same way. You describe what you want. The model writes code.
01:01GStack does something different. The first command isn't slash build. It's slash office hours.
01:08Before 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.
01:22Then the loop kicks in. Think, plan, build, review, test, ship, reflect.
01:30Each 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.
01:40Process beats prompts. And one command, slash auto plan, chains the entire review pipeline together. Type once.
01:48Get 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.
01:58What 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.
02:08And 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.
02:21The 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.
02:41One command, full 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 logical lines of code a day versus 14 back in 2013.
03:03810 times. He also says he runs 10 to 15 sprints in parallel.
03:08The caveat, he uses logical LOC, not raw. Because in his words, AI inflates raw.
03:16Whether 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?
03:26Probably not. YC's platform amplifies everything tan ships, and opinionation cuts both ways.
03:34If your workflow matches TANs, g stack is a gift. If it doesn't, you'll fight the framework.
03:41The 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.
03:53Andre Carpathi said it out loud. Quote, I don't think I've typed like a line of code probably since December, unquote.
04:02Gstack is what that sentence looks like when you write it down as code. And the meta punchline. Open the Gstack commit log.
04:11434 commits, roughly 10 human contributors, and 89 distinct coauthors, almost all of them clawed across basically every model version Anthropic released this year.
04:23The 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.
04:34Just don't ignore. An org chart is now a slash command.
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.

Frameworks

Named ideas worth stealing.

01:26model

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 forJoeFlow sessions panel, agent orchestration framing
00:29concept

Org Chart as Slash Commands

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

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

/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 forMorning launch session framing in JoeFlow
01:40concept

Process beats prompts

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

Steal forPositioning JoeFlow as a process layer, not a prompt box
CTA Breakdown

How they asked for the click.

04:30link
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.

Storyboard

Visual structure at a glance.

open, typing hands
hookopen, typing hands00:01
GitHub card, 100K
hookGitHub card, 100K00:05
ROLES, org chart
promiseROLES, org chart00:33
/office-hours reveal
value/office-hours reveal01:05
PROCESS BEATS PROMPTS wheel
valuePROCESS BEATS PROMPTS wheel01:41
/ship terminal mockup
value/ship terminal mockup02:35
810x bar chart
value810x bar chart02:58
critic tweets
valuecritic tweets03:33
AN ORG CHART IS NOW A SLASH COMMAND
ctaAN ORG CHART IS NOW A SLASH COMMAND04:27
Frame Gallery

Visual moments.