gstack

Verdict. Wins on breadth. I use it for real software work. I skip it for vault scripts, one-off shell commands, writing and small fixes, where the overhead isn’t worth it.

what it is

A Claude Code skill framework from Garry Tan with 40+ skills covering the whole shipping loop, think → plan → build → review → test → ship → reflect. Role-based specialists handle scope review, eng review, design review, DX review, security, QA and release. It installs with git clone and ./setup, and upgrades with /gstack-upgrade.

how I use it

Installed globally since April 2026, so it’s in every session.

• For anything non-trivial the path is /office-hours → /autoplan → implement → /review → /qa → /ship.
• /office-hours when I know the pain but not the shape. /autoplan when I want a reviewed plan. Straight to /plan-eng-review when the plan is already clear.
• /review and then /codex on anything I ship to other people, so two models look at it. They have different blind spots.
• /browse for all web navigation and screenshots.
• /careful, /freeze or /guard when the stakes are high.

what I found

• /cso runs an OWASP Top 10 and STRIDE security audit with an 8/10 confidence gate.
• /qa drives a real Chromium browser, fixes bugs with atomic commits and writes a regression test per fix.
• /design-html turns mockups into production HTML with reflowing text, using Pretext.
• /pair-agent coordinates with other agents over ngrok with scoped tokens.
• In April I planned to cherry-pick /cso, /qa and /design-html and skip the rest because of context bloat. I ended up installing the whole framework.
• No token-cost figure was published when I looked in April.

compared to

• superpowers wins on discipline. gstack wins on breadth.

	superpowers	gstack
Author	Jesse Vincent (Prime Radiant)	Garry Tan (YC)
Built for	Engineers writing production code	Founders shipping products solo
Core idea	TDD methodology and subagent-driven dev	A virtual eng team of role-based specialists
Install	Plugin marketplace, one command	git clone + ./setup
Process	spec → plan → red-green-refactor → review	think → plan → build → review → test → ship → reflect
Standout skills	subagent-driven-development with two-stage review	/cso, /qa, /design-html, /pair-agent