Don't Rush to Install gstack — First Think About Who Should Use It
gstack is a one-person engineering team. But the real leverage isn’t one person using a great tool — it’s the entire team absorbing the methodology behind the tool.
Background
On March 12, 2026, YC President Garry Tan open-sourced gstack — a set of 30+ Claude Code Slash Commands that let a solo developer ship product like a 20-person team. 600,000 lines of production code in 60 days. 69.7k GitHub stars in 30 days. The numbers are stunning.
But we didn’t rush to ./setup.
The first thing we did was clone it into an isolated directory, audit the setup script, and read the source of the core Skills line by line. Not because we don’t trust it — because we already have our own system, Synapse, an operating system for managing a 44-person AI team. The question wasn’t “should we use gstack” — it was “at what level should we use it.”
The Core Insight: Tool vs. Methodology
gstack’s 30+ Skills look like a pile of Slash Commands on the surface. Underneath is a complete software-engineering methodology:
/review
Not “look at my code” — a two-pass review checklist (CRITICAL + INFORMATIONAL) plus a Fix-First auto-repair flow.
/qa
Not “run the tests” — a closed loop of browser test → bug found → atomic fix → auto-generated regression test → verification.
/ship
Not “push my code” — the full SOP: sync → merge → test → coverage audit → PR → deploy → monitor.
/cso
Not “check security” — OWASP Top 10 + STRIDE threat modeling + secrets archaeology + supply-chain audit.
Key realization: these methodologies are separable from the gstack tool itself. You can choose not to install gstack, but internalize the methodologies into your team.
Comparing the Two Paths
| Path | Description | Effect |
|---|---|---|
| Path A: Install the tool | Individual developer installs gstack, uses Slash Commands to work | One person gets stronger |
| Path B: Absorb the methodology | Decompose gstack methodologies and inject into every team role | The whole team gets stronger |
We chose Path B.
The mechanics: decompose gstack’s 30+ Skills by role, mapped to the R&D team’s 5 roles:
gstack Skill → Team Role
────────────────────────────────────────
/plan-eng-review → Tech Lead (architecture review)
/review → Tech Lead + QA (code review)
/cso → QA Engineer (security audit)
/qa → QA Engineer (browser testing)
/ship + /land-and-deploy → DevOps (one-click deploy)
/canary → DevOps (deployment monitoring)
/design-review → Frontend Dev (design audit)
/benchmark → QA + DevOps (performance baseline)We then created a Slash Command per role (/dev-plan, /dev-review, /dev-qa, /dev-ship, /dev-secure) which, when invoked, activates that role’s upgraded capability set.
Practical Result
In one day we completed:
- 5 Agent role upgrades: each role gained 3-4 methodology-level capabilities
- 5 R&D Slash Commands: shifted from “tell the AI what to do” to “the AI knows how to do it”
- R&D team total capabilities grew from 25 to 48 (+92%)
The key change isn’t quantity — it’s quality. Take QA Engineer:
Before upgrade
“Automated test framework setup”
After upgrade
“Browser-automation real-test workflow (Playwright real browser → bug found → atomic fix → auto-generated regression test → verification loop)”
The first is an activity description. The second is methodology. The first says “I can do it.” The second says “I do it according to this defined process.”
When Do You Install the Tool, and When Do You Absorb the Methodology?
- Solo developer, side project, hackathon → install gstack directly, 30 seconds to value
- Existing team system, multi-person collaboration, quality requirements → decompose methodology, infuse into roles, build your own commands
- Both → absorb methodology at team level; use gstack directly on personal projects; they don’t interfere
Conclusion
gstack’s biggest value isn’t the 30 Slash Commands — it’s the software-engineering methodology that Garry Tan and Claude distilled together. Tools can be replaced; methodology can be absorbed.
Don’t just install the tool. Install the way of thinking.
This article is part of the Synapse series — documenting how Janus Digital builds and operates with an AI-first methodology.