gstack

gstack is a directory of Markdown skills plus TypeScript helpers, installed under ~/.claude/skills/gstack for Claude Code or generated into each other host's skills directory by ./setup. The skills are the orchestration: a sprint sequence in which /office-hours writes a design doc that /plan-ceo-review reads, /plan-eng-review writes a test plan that /qa picks up, and /ship runs the release steps. The host agent executes each skill; gstack has no scheduler.

Multiple agents appear in three places. Running several sprints in parallel is left to an external tool, Conductor, which the README says runs Claude Code sessions in isolated workspaces. /pair-agent and the OpenClaw integration coordinate separate agents through a shared browser or through OpenClaw spawning Claude Code sessions. Outside reviews call the other vendor's CLI. The sidebar agent is a child Claude instance in an isolated session.

State is local. Skills hand results to each other through design and test-plan files, a browser daemon keeps tabs and cookies between calls, and an optional GBrain knowledge base gives cross-session memory, registered with Claude Code as an MCP server when the user chooses it.

Several skills are interactive: the design review asks one question per design choice, and the README says risky documentation changes return for approval. /careful warns before destructive commands, /freeze restricts edits to one directory, and an opt-in verify hook holds a turn open until a project's declared command passes, yielding after three blocked attempts. For the browser, a handoff command opens a visible Chrome at the same page when the agent hits a CAPTCHA or login, and resumes after the user finishes. Telemetry is opt-in and every off-machine send is logged to a local receipt file.

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

# Claude Code: install
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack \
  && cd ~/.claude/skills/gstack && ./setup

# Other agents: clone anywhere, let setup detect hosts or name one
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/gstack
cd ~/gstack && ./setup --host codex

# Then, inside the agent
/office-hours      # describe what you are building
/plan-eng-review   # lock architecture and tests
/review            # review the branch
/qa                # test against a staging URL
/ship              # release steps

• Requires Claude Code, Git and Bun 1.0 or newer (Node.js on Windows only).
• /cso needs a Bun release with four --no-compile-autoload-* build flags and a native toolchain; without them setup skips the CSO helpers and /cso reports not assessed.
• The README's install prompt asks Claude to add a gstack section to CLAUDE.md that forbids the claude-in-chrome MCP tools in favour of /browse.
• Open issues report a Playwright Chromium download failure aborting setup, a generated Codex ship skill over a 160 KB token ceiling, and a broken Cursor host setup.
• /claude was renamed to /claude-code; re-run ./setup --host <name> to migrate managed installs.
• Under Conductor, API keys are stripped from workspace environments, so set the GSTACK_-prefixed key variables described in the README.

Only partly and optionally. /setup-gbrain can register the separate GBrain server with Claude Code as an MCP server. gstack ships no MCP server, and its install prompt tells Claude to use /browse instead of the claude-in-chrome MCP tools.

Not on its own. The skills are roles followed by the host agent in sequence. Parallel sessions come from Conductor, which the README recommends, while /pair-agent and the OpenClaw integration connect separate agents through a shared browser or through OpenClaw spawning Claude Code.

Claude Code first. The README lists setup hosts for Codex CLI, OpenCode, Cursor, Factory Droid, Kiro, Slate, OpenClaw, Hermes and GBrain, and an instruction-only digest for others.

Yes. The repository is MIT licensed and the README says it is free. Telemetry is opt-in, and the optional Aside browser and any model API usage are separate.

Both are skill packs with a fixed workflow. gstack centres on named roles and slash commands plus a browser layer for QA, while Superpowers centres on a plan-and-subagent workflow that its skills trigger automatically.