Graphic tutorial: 4 steps to turn Claude Code into a virtual engineering team, from/office-hours to/ship图文教程：四步把 Claude Code 变成虚拟工程团队，从 /office-hours 到 /ship 全流程

Front: Install Claude Code, Git, Bun v1.4.2+ (Node.js is required for Windows users).

Paste this command in Claude Code: git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack & & cd ~/.claude/skills/gstack & &./setup

setup builds the tool and downloads the browser kernel, which takes about a few minutes for the first time; when finished, follow the prompts to write the gstack skill manifest into CLAUDE.md, so that each session can use the full slash command directly.

Open a new session, enter/office-hours, and describe in vernacular what you're going to do: the target user, the core features, why not the existing plan?

The "CEO" role will ask you the key trade-offs (which piece to do first, what to cut), and after the chat, a clear page of product direction instructions will be produced, which is much faster than your own hard thinking about the empty prompt.

Turn ideas into plans: run/plan-ceo-review on any function point (CEO perspective), then run/plan-eng-review (engineering manager locking architecture, fixing module boundaries), and finally/plan-design-review gateway interaction and vision.

After writing the code, take three reviews:/review to let senior reviewers find production-grade bugs;/design-review to grasp the details of the interface;/deslop-shared-libs to clean up the kind of abstraction layer that AI loves to write "looks advanced but redundant".

Acceptance:/qa followed by a staging address or local API/CLI/webhook, the QA supervisor will open the browser step by step to verify, and the list of bugs will be listed for you to confirm.

Release: After the test is passed, run/ship or/land-and-deploy, the release engineer will handle the submission, merging and deployment; after going online,/canary grayscale observation,/retro review and precipitation experience.

Security plus points: For items involving login, payment, and user data, run/cso for OWASP + stride audit once before release (additional compilation environment is required, and not assessed will be explicitly prompted).