README

gstack

gstack turns Claude Code (and other coding agents) into a virtual engineering team: a CEO who rethinks the product, an eng manager who locks architecture, a designer who catches AI slop, a reviewer who finds production bugs, a QA lead who opens a real browser, a security officer who runs OWASP + STRIDE audits, and a release engineer who ships the PR. All slash commands, all Markdown, all free, MIT license.

I'm Garry Tan, President & CEO of Y Combinator. This is the open source software factory I use every day, and I'm sharing it because these tools should be available to everyone. The story, the productivity numbers and how I run ten sprints at once are in Why gstack.

Fork it. Improve it. Make it yours. And if you want to hate on free open source software — you're welcome to, but I'd rather you just try it first.

Who this is for:
- Founders and CEOs — especially technical ones who still want to ship
- First-time Claude Code users — structured roles instead of a blank prompt
- Tech leads and staff engineers — rigorous review, QA, and release automation on every PR

 What gstack is for

- A whole team's judgment for one builder. Product, design, engineering, QA, security and release reviews, each from a specialist role.
- Catch what CI misses. Find the bugs that pass tests but break in production, before they ship.
- AI-written changes you can trust. Every change carries its tests, its review and the evidence for both, so you can merge without rereading every line.
- Free, open and portable. MIT-licensed, and it runs on Claude Code and the other major coding agents.

 Quick start

1. Install gstack (two pastes, about 30 seconds of setup; see below).
2. Run /office-hours and describe what you're building. It pushes back on your framing and writes a design doc the other skills read.
3. Run /review on any branch with changes. It finds the bugs that pass CI but break in production, and fixes the obvious ones.
4. Run /qa on your staging URL, or on an isolated local API, CLI, job or webhook. It opens a real browser, reproduces bugs and fixes them.

Stop there. You'll know if this is for you. When you want the whole sprint, /autoplan reviews a plan end to end and /ship runs tests, review and the PR.

 Install — about 30 seconds

Requirements: Claude Code, Git, Bun v1.4.2+ (the tested version; setup refuses Bun older than 1.3.3, which would let compiled tools read a project's .env), and Node.js on Windows. Recommended on macOS: the Aside browser (macOS 15+), which the browser skills, /make-pdf and /diagram drive first with your real logged-in sessions; without it, ./setup builds gstack's own bundled browser. /cso needs a native toolchain as well; setup says so and leaves it unavailable when the toolchain is absent. Timing, the /cso prerequisites and the hooks setup registers: docs/install.md.

 Step 1: Install on your machine

Open Claude Code and paste this. Claude does the rest.

 Install gstack: run git clone --single-branch --depth 1 https:/

Top issues

Latest release

gstack v1.98.0.0 (regular release)

1 version since v1.97.0.0, one line each. Compare or read the full changelog.

New installs and team-mode installs follow the stable branch, which now points here; gstack-config set update_channel main follows every merge instead (docs/releases.md).
- 1.98.0.0 (2026-11-07): An opt-in /autoplan gate that holds the session until the pipeline finishes (GST-1666).