Garry Tan’s gstack is an open-source toolkit with distinct skills for product planning, code review and browser QA. The planning skill questions the premise, the reviewer reads the diff, and browser QA works through the interface. gstack repository
Start with one planning skill
In Claude Code, open /office-hours and describe the screen you want to change and the difficulty visitors have today. With the experimental Codex install, ask the agent to use gstack-office-hours. Commands and enforcement vary by host. Host support
Our tools section will cover skills and open source.
One guide can belong to both topics.
Before splitting the navigation, examine how readers would look for a guide.Choose the installation for your agent
Check the official guide for prerequisites such as Git and Bun. Clone the repository and run setup from inside it, using the command for your agent.
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/gstack
cd ~/gstack
./setup --host claudeFor Codex only, change the final line to ./setup --host codex. Run ./setup --status to inspect the registered hosts and their status. Official installation guide
Give review and QA a target
%% Three ways to inspect the same screen
flowchart TD
A["Planning: how will readers find a guide?"]
A --> B["Review: inspect category links and the diff"]
B --> C["QA: switch categories and go back on mobile"]For a code change, point /review at the diff and name the regression you care about. For browser QA, give it the URL and the steps. One test for the tools page would be to select a category on mobile and use Back to return to the same list.
/ship can go from tests and review to pushing a branch and opening a pull request. Set the target branch and what may be shared before handing off that step. gstack skill reference