Full Byte Developer.
SPRINT

Run a Claude Code sprint with gstack

Use gstack's planning, review and QA skills in order, after reviewing the installer's hooks.

Published · 2 sources

Garry Tan's gstack gives Claude Code separate skills for planning, code review and QA. The repository documents a sprint that passes work between them [1].

Review setup and install

The install docs require Claude Code, Git and Bun, and recommend Bun v1.4.2 or later. Windows also needs Node.js [2].

Warning: ./setup registers hooks in ~/.claude/settings.json, including a default Stop hook. Review the installer's hook details before running it [2].

The repository's personal install command is [1]:

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

Describe the problem before building

In Claude Code, run each skill separately and answer its questions before continuing. The documented order is [1]:

text
/office-hours
/plan-ceo-review
/plan-eng-review

You should get a design document from /office-hours and an engineering plan covering data flow and tests from /plan-eng-review [1]. Approve the plan before asking Claude to build.

Review and test the changes

After implementation, run these separately. Give /qa your staging URL or an isolated local target [1]:

text
/review
/qa

The README says both skills can fix code, so inspect their changes [1].

Ship and review the sprint

Warning: /ship runs the release workflow, including tests and a pull request. Use it when the changes are ready [1].

text
/ship

For the repository's retrospective workflow, run [1]:

text
/retro

You can use that report to choose what to change in the next sprint [1].

Keep this guide

By Full Byte Developer

Original posts: TikTok video, Instagram reel

Filed under Claude Code, Dev tools

Sources

Next in this stack