Chris EichlerAI-first Product
& Marketing

Silicon Valley AI Setup

Tan's claim: with gstack he ships at a run rate of ~810× his 2013 pace (logical lines/day, not raw LOC). In 60 days he shipped 3 production services and 40+ features solo — on the side of his full-time YC job.

Repo: github.com/garrytan/gstack — MIT, free, no premium tier.


Why it matters

The tool is process-driven, not just a collection of prompts. The skills run in the order of an actual sprint:

Think → Plan → Build → Review → Test → Ship → Reflect

Each skill feeds the next:

  • /office-hours writes a design doc → read by /plan-ceo-review
  • /plan-eng-review writes a test plan → consumed by /qa
  • /review finds bugs → /ship verifies the fixes

For solo founders with the classic "too many projects at once" energy, this is the structure that's been missing.


Install (30 seconds)

Prerequisites

Step 1: Install on your machine

Open Claude Code and paste this prompt — Claude handles the rest:

Install gstack: run `git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup` then add a "gstack" section to CLAUDE.md.

Step 2: Team mode (for shared repos, recommended)

From the repo root:

(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"

No vendoring, no version drift, automatic update check per session (throttled to 1×/hour, silent).

Other agents

gstack runs on 10 AI coding agents — not just Claude. Setup auto-detects what you have installed:

git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/gstack
cd ~/gstack && ./setup

Target a specific one with ./setup --host <name>: Codex CLI, OpenCode, Cursor, Factory Droid, Slate, Kiro, Hermes, GBrain.


Best use — the sprint flow

Quick Start (5 steps)

  1. Install (see above)
  2. /office-hours — describe what you're building. Tan's "YC Office Hours" skill asks 6 forcing questions that reframe your idea before you write code.
  3. /plan-ceo-review on any feature idea — finds the 10-star product hidden in your request.
  4. /review on any branch with changes.
  5. /qa on your staging URL — opens a real browser, clicks through flows, finds bugs, fixes them, generates regression tests.

The most important skills at a glance

SkillRoleWhat it does
/office-hoursYC Office Hours6 forcing questions, reframes your product before coding
/plan-ceo-reviewCEO/FounderFinds the 10-star product. 4 modes: Expansion, Selective, Hold, Reduction
/plan-eng-reviewEng ManagerArchitecture, data flow, edge cases, tests — before coding
/plan-design-reviewSenior DesignerRates every design dimension 0–10, AI-slop detection
/autoplanReview pipelineOne-shot: CEO → Design → Eng → DX, fully automated
/reviewStaff EngineerFinds production bugs, auto-fixes obvious ones
/qaQA LeadReal browser, real clicks, fixes bugs, regression tests
/csoChief Security OfficerOWASP Top 10 + STRIDE threat model, 0 false positives
/shipRelease EngineerSync, tests, coverage audit, PR — end-to-end
/land-and-deployRelease EngineerMerge PR, wait for CI, check production health
/design-shotgunDesign Explorer4–6 AI mockup variants, comparison board, iteration
/design-htmlDesign EngineerMockup → production-ready HTML/CSS, framework-aware
/investigateDebuggerRoot-cause debugging, Iron Law: no fix without investigation
/codexSecond OpinionIndependent review via OpenAI Codex CLI
/careful /freeze /guardSafetyProtection against destructive commands & accidental edits

What sets it apart

Parallel sprints. With tools like Conductor you can run 10–15 Claude Code sessions simultaneously — each in its own workspace. One session runs /office-hours for a new idea, another /review on a PR, a third implements a feature, a fourth tests via /qa. The sprint structure is what makes parallelism possible in the first place.

Smart review routing. CEO review for a backend bugfix? Unnecessary. Design review for infra changes? Also no. gstack automatically detects which reviews are appropriate.

Browser eyes. /qa opens a real Chromium, clicks through flows, finds bugs, fixes them atomically with regression tests. /open-gstack-browser gives you a dedicated browser variant with anti-bot stealth, sidebar agent and cookie import.

Ideas on AI-first Product Management & Marketing, straight to your inbox.

No spam, unsubscribe at any time

Chris Eichler