The GStack Sprint Workflow: Think → Plan → Build → Review → Test → Ship
Garry Tan's structured end-to-end sprint process for Claude Code — from product discovery through code review, QA testing, and shipping a PR. A repeatable workflow any developer can follow.
This workflow is the core process behind GStack — Garry Tan's open-source Claude Code system. It structures how you go from an idea to shipped code using Claude Code as your virtual engineering team.
The Sprint Process:
Step 1 — THINK (/office-hours): Start by describing what you want to build. The /office-hours skill acts like a YC office hours session — it asks six forcing questions, pushes back on your framing, challenges your premises, and often reframes your idea into something bigger and better. It writes a design doc that feeds into everything downstream.
Step 2 — PLAN (/plan-ceo-review → /plan-eng-review → /plan-design-review): Three separate reviews happen on your plan. The CEO review rethinks the product scope and finds the "10-star" version. The Eng review locks architecture with ASCII diagrams, data flow, edge cases, and test plans. The Design review rates each design dimension 0-10 and catches AI slop.
Step 3 — BUILD: With a reviewed and approved plan, Claude Code writes the implementation. Because the plan is thorough, the code is more focused and correct from the start.
Step 4 — REVIEW (/review): A Staff Engineer review that catches bugs which pass CI but break in production. Auto-fixes obvious issues and flags completeness gaps.
Step 5 — TEST (/qa): The QA Lead opens a real Chromium browser, clicks through your app's flows, finds bugs, fixes them with atomic commits, and auto-generates regression tests for every fix.
Step 6 — SHIP (/ship): The Release Engineer syncs main, runs tests, audits coverage, pushes code, and opens a PR. If you don't have a test framework, it bootstraps one.
Why this matters: Most people use Claude Code as a blank prompt — type a request, get code. This workflow gives you a structured, repeatable process that catches bugs early, ensures quality, and ships reliably. Each step feeds into the next, so nothing falls through the cracks.
Based on Garry Tan's GStack (github.com/garrytan/gstack). MIT licensed, free and open source.
## Installation
1. Install GStack first (see the GStack resource for full install) 2. Open Claude Code in your project 3. Run: /office-hours — describe what you're building 4. Run: /plan-ceo-review — get product-level review 5. Run: /plan-eng-review — lock the architecture 6. Approve the plan, then let Claude build 7. Run: /review — catch production bugs 8. Run: /qa https://your-staging-url.com — real browser QA 9. Run: /ship — tests, coverage audit, PR
## Comments (0)
No comments yet. Be the first to share your thoughts.