# AI use cases for Gstack (garrytan/gstack) Repo: [garrytan/gstack](https://github.com/garrytan/gstack) | Use cases: 3 | Page: https://dedupedai.com/use-cases/garrytan-gstack/ gstack is Garry Tan's open source Claude Code setup: slash command skills that act as a virtual engineering team, including a CEO who rethinks the product (/office-hours), a reviewer who finds production bugs (/review), a QA lead who opens a real browser (/qa), a security officer (/cso) and a release engineer (/ship). It installs for Claude Code by default and for Codex, OpenCode, Cursor and other agents with --host. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Pressure-test a product idea with /office-hours before you build: https://dedupedai.com/use-cases/garrytan-gstack/pressure-test-a-product-idea-with-office-hours/ - Find production bugs with /review and /qa before you ship: https://dedupedai.com/use-cases/garrytan-gstack/review-and-qa-a-branch-with-gstack/ - Roll out Gstack to your whole team with team mode: https://dedupedai.com/use-cases/garrytan-gstack/roll-out-gstack-to-a-team-repo/ ## How to pressure-test a product idea with /office-hours before you build with Gstack Repo: [garrytan/gstack](https://github.com/garrytan/gstack) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README Describe what you want to build and let Gstack push back on the framing and write a design doc. **Who it is for:** A technical founder about to spend a week building the wrong version of an idea. **The problem:** It is easy to build exactly what you described instead of what users need, and nobody challenges the premise. **The outcome:** A design doc with challenged premises and implementation approaches that the other Gstack skills read automatically. ### Steps 1. Open Claude Code and install Gstack: `git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup` 2. Run `/office-hours` and describe what you are building with specific examples of the pain 3. Agree, disagree or adjust as it challenges your premises and proposes approaches 4. Run `/plan-ceo-review` and `/plan-eng-review` to challenge scope and lock the architecture 5. Approve the plan and let Claude build from the design doc ### Prompt to paste into your agent ```text Install garrytan/gstack and run /office-hours on this idea: . Push back on my framing, write the design doc, then run /plan-ceo-review and /plan-eng-review and summarize what changed before writing any code. ``` ### Caveat Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/garrytan-gstack/pressure-test-a-product-idea-with-office-hours/ ## How to find production bugs with /review and /qa before you ship with Gstack Repo: [garrytan/gstack](https://github.com/garrytan/gstack) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Run Gstack's reviewer on a branch and its QA lead on your staging URL, then ship the PR. **Who it is for:** A tech lead who wants every PR reviewed and clicked through in a real browser without doing it by hand. **The problem:** Bugs that pass CI still break in production, and manual QA on every branch does not scale. **The outcome:** A reviewed branch with obvious issues auto-fixed, bugs reproduced in a real browser and a PR opened by /ship. ### Steps 1. Install Gstack in Claude Code as in the quick start 2. Run `/review` on any branch with changes; it fixes the obvious issues and asks before risky ones 3. Run `/qa` on your staging URL to open a real browser, reproduce bugs and fix them 4. Run `/ship` to run tests, review and open the PR 5. Check installs anytime with `./setup --status` ### Prompt to paste into your agent ```text Using garrytan/gstack, run /review on this branch and auto-fix only the obvious issues. Then run /qa against , report each bug with steps to reproduce, and run /ship only after I approve the fixes. ``` ### Caveat Risk, credentials: On macOS the browser skills drive the Aside browser with your real logged-in sessions; point /qa at staging, not production accounts. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/garrytan-gstack/review-and-qa-a-branch-with-gstack/ ## How to roll out Gstack to your whole team with team mode with Gstack Repo: [garrytan/gstack](https://github.com/garrytan/gstack) | Difficulty: Intermediate | Time: 20 minutes | Basis: From the README Switch a shared repo to team mode so every teammate's Claude Code gets Gstack and auto-updates. **Who it is for:** An engineering manager who wants the same agent workflow for everyone without vendoring files. **The problem:** Each developer has a different agent setup, and manual upgrades drift out of date. **The outcome:** A committed repo bootstrap that requires (or nudges) Gstack for AI-assisted work, following the weekly stable channel. ### Steps 1. Install Gstack on your own machine first 2. From inside the repo run the team mode command from the README: `(cd ~/.claude/skills/gstack && ./setup --team) && ~/.claude/skills/gstack/bin/gstack-team-init required && git add .claude/ CLAUDE.md && git commit -m "require gstack for AI-assisted work"` 3. Swap required for optional if you want to nudge teammates instead of blocking them 4. Teammates on Codex or Cursor install with `cd ~/gstack && ./setup --host auto` 5. Follow every merge instead of weekly releases with `gstack-config set update_channel main` ### Prompt to paste into your agent ```text Set up garrytan/gstack team mode in this repo with the optional setting, commit the change, and write a short note for teammates on how to install it for Claude Code or with --host for Codex and Cursor. ``` ### Caveat Team mode's required hook runs on Node.js, so every teammate needs Node.js on PATH. Hosts other than Claude Code are marked experimental. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/garrytan-gstack/roll-out-gstack-to-a-team-repo/