Skip to content
aicoolies logo

GStack Review: YC CEO Garry Tan's Claude Code Skill Pack Turns One Agent Into a Virtual Engineering Team

GStack provides 23 opinionated slash commands for Claude Code that assign specialist roles from CEO product review to QA testing with a real browser. Created by Y Combinator CEO Garry Tan, it enforces structured development phases that prevent the quality drift common when AI handles planning, coding, and review in a single pass. The persistent Chromium daemon and design pipeline are standout features no other skill pack matches.

reviewed by Raşit Akyol April 3, 2026

Documented evidence

rubric editorial-review-v1

This review is grounded in documented sources and repository analysis. It does not claim a unique hands-on reproducibility record.

Sources checked

Verdict

GStack is the most complete Claude Code skill pack available, combining role-based development phases with a persistent browser for QA and a unique design pipeline. It excels for solo developers and small teams shipping full-stack products, though the Claude Code exclusivity limits its reach. The opinionated workflow requires buy-in but delivers measurable productivity gains for those who commit to the structured approach.

88/100

overall

Speed85
Privacy95
Dev Experience90

What GStack Does

GStack arrives at a moment when AI coding skill packs are proliferating rapidly, but few carry the weight of real-world production validation behind them. The public repository and README provide the audit trail for these commands, so this review treats them as source-disclosed workflows rather than independently verified productivity benchmarks. The 112K+ GitHub stars accumulated in weeks reflect both Tan's profile and genuine developer interest in structured AI workflows.

Role Separation and QA Automation

The role separation philosophy is the conceptual core of GStack and what makes it genuinely useful rather than just another prompt collection. Running plan-ceo-review forces Claude into product strategy mode where it evaluates feature scope and user impact without touching implementation details. Switching to plan-eng-review shifts the cognitive mode entirely toward architecture, data flow, and edge case analysis. This separation prevents the quality dilution that happens when a single agent context handles every development phase simultaneously.

The QA skill with its persistent Chromium daemon is arguably GStack's most impressive technical achievement. Unlike one-shot browser tools that cold-start a new instance per command, GStack maintains a headless browser session with README-described ~100ms-per-command interactions that retains cookies, tabs, and localStorage across interactions. The qa command reads your git diff, identifies affected pages, opens them in the browser, tests functionality, fixes bugs with atomic commits, and re-verifies. This closed-loop QA cycle is what enabled scaling from 6 to 12 parallel coding sessions.

Design Pipeline and Safety Guardrails

The design workflow pipeline fills a gap no other Claude Code tool addresses. Design-consultation researches competitive landscapes and builds design systems from scratch, while design-shotgun generates multiple visual variants with a side-by-side comparison board. Design-html then produces responsive production layouts using Pretext that actually reflow on resize rather than breaking at different viewport sizes. The design-review skill scores outputs on an 80-item checklist and flags AI-generated visual patterns, giving developers concrete feedback rather than subjective assessments.

Safety guardrails show thoughtful engineering for production environments. The careful command intercepts destructive operations before execution, covering rm -rf, DROP TABLE, force-push, and git reset --hard while whitelisting common build cleanups. Freeze restricts file edits to a specified directory boundary during debugging sessions, and guard combines both protections. These are simple mechanisms but they prevent the most common catastrophic mistakes when agents operate autonomously across multiple parallel sessions.

Installation and Productivity Analytics

Installation simplicity is a genuine advantage over more complex alternatives. A single copy command places the skill files into your project repository, and the setup script builds the Chromium binary and registers all slash commands. No package manager, no Docker container, no external service. The files commit directly to version control, meaning git clone on any team member's machine gives them the full GStack setup without additional configuration steps.

The retro skill provides productivity analytics that close the feedback loop on development velocity. It tracks lines added, commits, shipping velocity, test ratios, and PR sizes across all parallel sessions. This data-driven retrospective capability helps developers identify which skill combinations and workflow patterns produce the best results, turning GStack usage into an iterative optimization process rather than a static configuration.

Cross-Model Review and Limitations

Cross-model review through the codex skill adds a valuable second opinion from OpenAI's Codex CLI. Three modes cover standard code review with pass/fail gating, adversarial challenge where Codex actively tries to break the code, and open consultation with session continuity. When both the built-in review and codex skills have run, a cross-model analysis surfaces disagreements between Claude and Codex, catching issues that either model alone might miss.

The limitations are worth acknowledging honestly. GStack works exclusively with Claude Code, offering zero compatibility with Cursor, Codex, or other AI coding tools. The copy-based installation model works well for individual developers but creates drift when different repositories need different review gates or QA configurations. The skill files are opinionated by design, and customizing them requires understanding the Markdown-based skill configuration format that is well-documented but has a learning curve.

The Bottom Line

GStack delivers on its core promise of turning Claude Code into a structured engineering team rather than a generic assistant. The design pipeline and browser-based QA are genuinely unique capabilities that no competing skill pack offers. For solo developers and small teams shipping full-stack products with Claude Code, GStack represents one of the most practical productivity multipliers available. The MIT license and Tan's commitment to keeping it free remove the typical friction of adopting developer tooling.

Pros

  • Persistent Chromium daemon delivers README-described ~100ms-per-command browser automation with cookie and session persistence across commands
  • Design pipeline with design-consultation, design-shotgun, and design-html has no equivalent in any competing tool
  • Safety guardrails prevent destructive operations and restrict file edits during debugging with zero configuration overhead
  • Cross-model code review via Codex integration catches issues that single-model review misses consistently
  • Zero-dependency installation copies Markdown files directly into the project with no Docker or package manager needed
  • Retro skill tracks productivity metrics across parallel sessions enabling data-driven workflow optimization
  • MIT license and commitment from YC CEO ensures long-term maintenance and active community development

Cons

  • Works exclusively with Claude Code offering zero compatibility with Cursor, Codex, or other AI coding editors
  • Copy-based installation creates configuration drift when multiple repositories need different skill variations
  • Customizing skill behavior requires understanding the Markdown-based configuration format and its conventions
  • Heavy reliance on parallel sessions means the full value requires a Claude Code subscription with high usage limits
  • No built-in task management or project tracking capabilities beyond the retrospective analytics skill

View GStack on aicoolies

Pricing, platforms, and community stacks — explore the full tool page

Comparisons with GStack

GStack logo
GStack
vs
Everything Claude Code logo
Everything Claude Code

GStack vs Everything Claude Code — Role-Based Skills vs Comprehensive Agent Harness

GStack and Everything Claude Code represent two distinct philosophies for supercharging AI coding agents. GStack provides 23 role-based slash commands created by YC CEO Garry Tan that turn Claude Code into a virtual engineering team, while ECC delivers a comprehensive agent harness with 30 subagents, 136 skills, and AgentShield security across multiple AI coding tools.

Alternatives to GStack

Agent harness performance system with 30+ agents and 136 skills

Everything Claude Code is a comprehensive agent harness performance optimization system providing 30 specialized agents, 136 skills, 60 commands, and automated hook workflows for AI-assisted development. Born from an Anthropic hackathon winner and evolved over 10+ months of intensive daily use, it works across Claude Code, Codex, Cursor, and OpenCode with built-in security scanning via AgentShield, continuous learning, and research-first development patterns.

Open Source

AI coding agent for embedded systems and firmware engineering

Embedder is a specialized AI coding agent for firmware and embedded systems development. It supports 400+ MCU variants including STM32 and ESP32, parses hardware datasheets to understand register maps and pin configurations, and verifies generated code by interacting with physical boards via serial console. YC S25 participant currently in beta.

paid

Multi-agent orchestration layer for OpenAI Codex CLI

Oh My Codex (OMX) transforms OpenAI Codex CLI into a coordinated multi-agent system. It layers workflow orchestration, persistent memory, team-based parallel execution via tmux worktrees, and a live HUD dashboard on top of standard Codex. OMX provides 30+ role-specialized agents and 40+ workflow skills covering planning, execution, verification, TDD, security review, and autonomous research loops.

Open Source

FAQ

How does GStack structure Claude Code into specialized engineering roles?

Decomposes engineering into modular roles (Architect, Developer, QA, Security), activating skills sequentially and passing structured markdown artifacts while evicting intermediate reasoning.

How does GStack maintain state and enforce quality gates between handoffs?

Relies on deterministic repository artifacts (.gstack/architecture.md, test manifests), allowing role transitions only when verification checks (green tests, linting) pass cleanly.

What are the token consumption trade-offs of using GStack?

Iterative multi-stage role pipelines consume 2x to 4x more tokens than single prompts, but drastically cut hallucinations and regressions on complex full-stack features.

Can GStack be customized with project-specific linters and CI commands?

Builds on Claude Code's native skill runtime, allowing teams to add custom shell skills, linter hooks (ESLint, Biome, Ruff), and automated CI test commands into role definitions.

Sources & verification

Sources checked
Content verified

Verification dates are editorial checks. Routine CMS saves and automatic updatedAt timestamps do not advance them.