Garry Tan's open-source workflow for Claude Code, Codex, and compatible agents.

Turn your coding agent into a software team with standards.

gstack adds a real delivery loop to agent-driven work: reframe the problem, lock the plan, review the code, run browser QA, ship cleanly, and learn from the sprint. You move faster without trusting a blank prompt.

  • 18 specialists
  • 7 power tools
  • MIT licensed
  • 30-second install

Sprint Shape

gstack logo
  1. 01

    Think

    /office-hours turns a feature request into a sharper problem, a better wedge, and a design doc the rest of the stack can use.

  2. 02

    Plan

    /plan-ceo-review, /plan-eng-review, and /plan-design-review pressure-test scope, architecture, UX, and tests before code starts.

  3. 03

    Build

    Implementation runs against a real brief instead of improvised prompts and shifting intent.

  4. 04

    Review

    /review inspects the branch like a senior engineer looking for regressions, gaps, and hidden risk before prod does.

  5. 05

    Test

    /qa opens a real browser, walks the app like a user, fixes issues, and turns them into regression coverage.

Install snippet

30 seconds
git clone https://github.com/garrytan/gstack.git ~/.codex/skills/gstack
cd ~/.codex/skills/gstack && ./setup --host codex
Free and MIT licensed
Works with Claude Code and Codex
Browser QA built in
Review and release workflow included

Who it is for

For builders who want agent speed without lowering the engineering bar.

Audience 01

Founders & CEOs

Ship more product ideas without rebuilding an engineering org around every new bet.

Audience 02

First-time agent users

Start with named roles, concrete commands, and a system that tells you what to do next.

Audience 03

Tech leads & staff engineers

Add architecture review, regression pressure, browser QA, and release discipline to every branch.

Sprint workflow

A delivery system for AI coding, not a pile of prompts.

Think

/office-hours turns a feature request into a sharper problem, a better wedge, and a design doc the rest of the stack can use.

Plan

/plan-ceo-review, /plan-eng-review, and /plan-design-review pressure-test scope, architecture, UX, and tests before code starts.

Build

Implementation runs against a real brief instead of improvised prompts and shifting intent.

Review

/review inspects the branch like a senior engineer looking for regressions, gaps, and hidden risk before prod does.

Test

/qa opens a real browser, walks the app like a user, fixes issues, and turns them into regression coverage.

Ship

/ship handles the last-mile checks so branches land with tests, docs, and release discipline intact.

Reflect

/retro closes the loop with stats, patterns, and pressure for a better next sprint.

Six of the eighteen

These are the commands that make gstack useful every sprint.

Each one covers a job that usually gets skipped when teams chase raw agent speed: sharper framing, better plans, tougher review, real QA, and cleaner releases.

Product reframing

/office-hours

Pushes past the first idea, sharpens the wedge, and writes the brief downstream commands inherit.

Scope and ambition

/plan-ceo-review

Challenges the request, finds the stronger product move, and protects you from shipping a weak version.

Architecture and tests

/plan-eng-review

Turns hand-wavy intent into data flow, failure modes, edge cases, and a plan the code can actually follow.

Production-minded review

/review

Targets regressions, missing tests, and the issues happy-path implementation usually leaves behind.

Browser QA that can fix

/qa

Navigates your app in a real browser and converts discovered issues into concrete fixes and regression coverage.

Release automation

/ship

Runs the release checklist so code lands with the tests, docs, and process support it needs.

Quick start

Install once. Start with /office-hours. Use it on every branch.

  1. 01

    Clone the repo into your agent's skills directory.

  2. 02

    Run setup and let gstack register the commands for your host.

  3. 03

    Start with /office-hours so the rest of the sprint inherits a real brief.

  4. 04

    Use /review, /qa, and /ship before you merge.

Install command

Copy, run, then start with /office-hours.

git clone https://github.com/garrytan/gstack.git ~/.codex/skills/gstack
cd ~/.codex/skills/gstack && ./setup --host codex

FAQ

The questions serious builders ask before they install.

gstack is Garry Tan's open-source workflow for Claude Code, Codex, and compatible agents. It packages specialist commands and power tools into one software delivery system.
It is built for founders, first-time agent users, and technical leads who want AI speed without lowering the bar on planning, review, QA, and release quality.
Because raw speed is not the bottleneck. Trust is. gstack adds roles, order, review gates, QA, and release checks so each step inherits context from the one before it.
Yes. gstack is designed for Claude Code, Codex, and similar agent hosts, so the same workflow can carry product framing, review, browser QA, and release discipline across tools.
You can install it in about 30 seconds and get to a first useful run in a few minutes on a repo that already knows how to run tests.