What it is
gstack is a set of skills, slash commands, and helper tools for Claude Code. The author frames it as turning one AI assistant into a set of working roles: product review, engineering review, design, browser QA, security, shipping, and documentation.
The project is not an application framework. It is an organizational layer around AI-assisted coding: which commands to run, how to review a plan, how to connect a browser, how to review changes, and how to preserve project knowledge.
How it appeared and why it stuck
gstack grew out of Garry Tan’s personal process and was published as a repeatable setup. As AI coding tools grew, many people found that the missing piece was not another model but discipline: how to prevent the assistant from quickly writing the wrong thing, how to check results, and how to keep the product in view.
In that sense the project works like a public operating system for assistant-driven work. It provides roles and commands that can be read, edited, and moved into other projects.
What is inside
Inside are an installer, command flows, skills for planning, review, browser QA, investigation, documentation, security, Chrome connection, and knowledge indexing. There is a personal install mode and a team mode where a repository can require the setup.
A typical gstack start
This example shows the basic process commands: discuss the task first, review the plan, check changes, run browser QA, and then ship.
/office-hours
/plan-ceo-review
/review
/qa https://example.com
/shipWhere it helps
gstack helps developers who already work in Claude Code and want a stricter rhythm: clarify the product, check architecture, inspect the interface in a browser, and only then ship changes.
For a simple context-free edit, gstack may be heavy. Its value appears when AI performs many actions and the operator needs to keep control over direction.
Strengths and limits
The strength is practical completeness. One set includes not only roles but also commands for review, browser work, documentation, and shipping.
The limitation is its strong authorial style. gstack reflects one person’s process and tools, so a team may need adaptation rather than blind copying.