g/ gstack Hands-on Classroom

3 HOURS HANDS-ON LECTURE

Before you ask for code,
design your dev team.

An intro course where you install gstack in Codex and Claude Code, then plan, review and QA the same project to compare AI development workflows yourself.

  • ForGit beginners
  • ToolsCodex · Claude Code
  • Result10-step lab outputs

gstack workflow

Think → Plan
→ Review → Test
ready to practice
CEO ENG QA REVIEW

gstack isn't a coding model; it's a development workflow that gives AI roles, order and quality standards.

01 / ORIENTATION

Today you'll learn
a way of working more than commands.

01

Don't build right away

Check the user's problem and scope, and surface assumptions before building.

02

Split roles

Run product, tech, review and QA views as separate skills.

03

Verify results

AI output isn't the answer. Check it with files, Git diff and real behavior.

02 / 180-MINUTE ROADMAP

From install to QA,
one complete loop

Getting oriented

Understand gstack and the differences between the two run environments.

Environment check

Check Git, Bun, accounts and your terminal setup.

Install Codex · Claude

Install each tool and do a first read task in the project.

Install gstack

Register the skills in your chosen host and check the status.

Break

Learners with install problems catch up during this time.

Problem and plan

Run office-hours and plan-eng-review.

Review and QA

Experience the difference between a code view and a user behavior view.

Compare and reflect

Compare the two tools' results and write a plan to apply them to your PBL.

03 / SETUP

Same gstack,
different ways to call it

Learners pick one track and follow along. The instructor demos both environments side by side.

Beginner class standard

Windows learners first follow the Windows native install. WSL2 is an optional track for learners who need a Linux environment. Either way, install Codex·Claude·gstack in the same environment.

WINDOWS · START FROM ZERO

The full Windows process
for first-time installers

Go through the steps below one by one from the top. Don't type text like PS C:\Users\... before a command; type only what's inside the gray command box.

Terminal

A window where you give the computer commands as text.

PowerShell

The terminal built into Windows.

Commands

Copy it, paste it into PowerShell and press Enter.

WSL

An optional feature that runs Ubuntu Linux inside Windows.

Optional track

WSL2 Ubuntu

Use this when you need a uniform Linux dev environment or the native install is blocked.

PATH A Windows native install - default beginner track
  1. Open PowerShell

    Press the Windows key, search for PowerShell and run it. If you see PS C:\Users\username> in the window, you're good.

  2. Install Git and Node.js

    Paste the commands below one line at a time and press Enter.

    winget install --id Git.Git -e winget install OpenJS.NodeJS.LTS

    Expected result · After the install-complete message, close and reopen PowerShell.

  3. Install Bun

    powershell -c "irm bun.sh/install.ps1|iex"

    Open a new PowerShell and type bun --version; if a number appears, it worked.

  4. Install and log in to Codex

    powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"
    codex --version codex

    On first run, follow the on-screen steps to log in with one of the offered options, like a ChatGPT account.

  5. Install and log in to Claude Code

    winget install Anthropic.ClaudeCode
    claude --version claude doctor claude

    You need an account that can use Claude Code. If you only use one tool, you can skip this step.

  6. Check all install results at once

    git --version node --version npm --version bun --version codex --version claude --version

    If each line shows a version number, go to the next step.

  7. Download gstack

    git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git "$HOME\gstack" cd "$HOME\gstack"
  8. Register gstack in Codex·Claude Code

    .\setup.ps1 --host codex .\setup.ps1 --host claude .\setup.ps1 --status

    If you only use one tool, run only that host's command. If codex or claude appears in the status table, it worked.

  9. Open PowerShell in the ZIP lab folder

    Right-click the ZIP and choose Extract All. Open the extracted project folder, type powershell in File Explorer's address bar and press Enter.

    git init git add . git commit -m "Lab start state" git status
  10. Start the first lab

    # If you chose Codex codex # If you chose Claude Code claude

    Always check git status and git diff before and after AI work.

PATH B WSL2 Ubuntu install - optional track

What is WSL?

WSL stands for Windows Subsystem for Linux. It lets you run an Ubuntu terminal and Linux dev tools inside Windows. It isn't required to use gstack.

  1. Install WSL from an admin PowerShell

    wsl --install

    When the install finishes, restart your computer.

  2. First Ubuntu run

    Run Ubuntu from the Start menu and create a Linux username and password. It's normal that no characters show while you type the password.

  3. Install required tools in Ubuntu

    sudo apt update sudo apt install -y git curl unzip curl -fsSL https://bun.com/install | bash source ~/.bashrc
  4. Install Codex and Claude Code inside Ubuntu

    curl -fsSL https://chatgpt.com/codex/install.sh | sh curl -fsSL https://claude.ai/install.sh | bash
  5. Install gstack inside Ubuntu too

    git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/gstack cd ~/gstack ./setup --host codex ./setup --host claude ./setup --status
Don't mix environments

If you install only Codex on Windows and gstack in WSL, they use different home folders. Install everything on Windows or everything in WSL2 Ubuntu.

Check these first when stuck

Command not found

Close PowerShell completely, open a new one and try again.

setup.ps1 is blocked

Run it like powershell -ExecutionPolicy Bypass -File .\setup.ps1 --host codex.

Git commit name error

Set git config user.name "student" and a local email.

gstack skills don't show up

Quit Codex·Claude, open a new session and check .\setup.ps1 --status.

Bun isn't recognized

Open a new PowerShell and check bun --version again.

Windows security blocks it

Don't turn off security settings; tell the instructor and switch to the WSL2 track.

TRACK A · EXPERIMENTAL HOST

OpenAI Codex

Read and edit the project in the terminal, and name gstack skills in plain language.

macOS · Linux · WSL

curl -fsSL https://chatgpt.com/codex/install.sh | sh

npm alternative

npm install -g @openai/codex

Check install and log in

codex --version codex
Codex official install docs ↗
TRACK B · FULL HOST

Claude Code

gstack's officially supported environment; call the main skills with slash commands.

Homebrew

brew install --cask claude-code

npm alternative

npm install -g @anthropic-ai/claude-code

Check install and log in

claude --version claude doctor claude
Claude Code official install docs ↗

COMMON STEP

Install gstack

Get the gstack source from the official Git repository and register it in your chosen AI tool's skills folder.

1

Get the official repository

git clone --single-branch --depth 1 \ https://github.com/garrytan/gstack.git ~/gstack cd ~/gstack
2

Register in your chosen environment

# Codex ./setup --host codex # Claude Code ./setup --host claude
3

Check status

./setup --status

METHOD B · PROMPT-DRIVEN SETUP

Instead of typing commands yourself,
ask Codex to install it

Codex can check your current environment and suggest·run the needed commands. If it needs to write files or access the network, it asks you for permission based on the approval policy.

What you need first

Codex can't install itself. Finish installing and logging in to Codex CLI with the official install command above before starting this.

  1. Start Codex in your lab folder

    Open a terminal in an empty folder or the extracted lab folder and run Codex.

    # Windows PowerShell mkdir "$HOME\gstack-class" -ErrorAction SilentlyContinue cd "$HOME\gstack-class" codex # macOS · Linux · WSL mkdir -p ~/gstack-class cd ~/gstack-class codex
  2. Prompt 1 — check the environment only, don't install

    First, read-only, check the OS, shell, required tools and any existing install.

    PROMPT 01Environment check
    I'm getting ready to install gstack.
    First check the current operating system and shell,
    and check the Git, Bun and Codex versions and whether gstack is already installed.
    
    Don't install anything or change files yet;
    just show me the facts you found, what's missing, the install path to use
    and the plan of commands to run.
  3. Check the results

    Check that the OS and install path Codex shows match your real environment. Don't put passwords, API keys or auth codes in prompts.

    CODEX · Sample check result

    Environment Windows 11 / PowerShell 7

    Found Git 2.x, Bun 1.x, Codex CLI logged in

    Missing gstack not installed

    Plan Clone the official repository to C:\Users\student\gstack, then register the Codex host and check status

  4. Prompt 2 — run the install while approving

    If the check looks right, send the next prompt. When a network access or home folder write approval appears, read the command and path before allowing it.

    PROMPT 02Install gstack
    Based on the check you just did, install gstack for the Codex host.
    
    Conditions:
    1. Use only the official repository https://github.com/garrytan/gstack.
    2. On Windows native, use $HOME\gstack and setup.ps1;
       on macOS·Linux·WSL, use ~/gstack and ./setup.
    3. If a gstack folder already exists, don't overwrite or delete it; stop and tell me.
    4. Don't run destructive commands.
    5. If you need network access or to write to the home folder, ask for approval first.
    6. After installing, run the --host codex registration and the --status check.
    7. At the end, summarize the commands you ran, the install path and the status result.
  5. What to check in the approval window

    CommandIs it git clone or setup?SourceIs it the official garrytan/gstack address?PathIs it the gstack folder in my home?ScopeNo deletes or forced resets?

    If you see a command you don't know, don't approve it; ask "Explain what this command changes."

  6. Check the install result

    CODEX · Sample done result

    Install path C:\Users\student\gstack

    Registered host codex

    Status installed / skills linked

    Next step Quit Codex and run a gstack skill in a new session

    # After leaving Codex, in a new terminal cd "$HOME\gstack-class" codex
  7. First gstack prompt

    PROMPT 03Check install and first run
    First check whether you can use the gstack-office-hours skill.
    If you can, read this project and summarize:
    
    1. Target users
    2. The problem users face
    3. The smallest core feature
    4. Unverified assumptions
    
    Don't change any files yet.

    Expected result · office-hours questions start, or users·problem·assumptions are summarized. If it says it can't find the skill, fully quit Codex and run it again in a new session.

04 / DOWNLOAD & PRACTICE

Get one step at a time,
and record results.

We don't use a GitHub lab repository. Download the ZIP, extract it and create a local Git repository.

ZIP

Download lab files

→
DIR

Extract and move in

→
GIT

Create a local baseline

→
AI

Run Codex or Claude

cd downloaded-lab-folder/project git init git add . git commit -m "Lab start state" git status
01

15 MIN · Setup

Environment check

Scripts to check Git, Bun, Codex and Claude versions, plus a learner checklist.

  • Environment check script
  • Install results checklist
  • Issue notes
Download Step 1 ZIP ↓
03

25 MIN · Plan

Tech plan review

Review components, data flow, exceptions and tests with plan-eng-review.

  • Same project baseline
  • Tech plan prompt
  • Plan review worksheet
Download Step 3 ZIP ↓
04

20 MIN · Verify

Code review and QA

See the difference between review and qa-only views and write a reproducible report.

  • Project with built-in defects
  • Review·QA run guide
  • QA report template
Download Step 4 ZIP ↓

INSTRUCTOR & OFFLINE PACK

Get all lab materials at once

The 10-step materials, sample app and worksheets in one ZIP.

Download full lab pack

05 / PROMPT LAB

The tools differ,
but the review standards are the same.

Codex prompt
Use the gstack-office-hours skill to review this project.

1. Target users
2. The problem to solve
3. Core value
4. The smallest core feature
5. Unverified assumptions

Don't change the code yet.
Shared lab rules

Check git status and git diff before and after work, and verify AI's explanations with the real files and run results.

06 / FULL LIFECYCLE LAB

From planning to QA,
connected in one project.

If the 3-hour intro course above is about install and first experience, this course is a follow-up lab applying it to your PBL. Each step ends with commands, human decisions, outputs and pass conditions.

Lab project

Assume you're adding empty-input prevention, duplicate prevention and long-title handling to the Focus List app. Don't change code in the planning and plan stages; changes start at the build stage.

How to read the sample results

The green result boxes below are examples of what you might get when you run the commands. They aren't answer keys to copy; use them to check your own result isn't missing users, evidence or verification conditions.

01DISCOVER

Problem·users

→
02SPEC

Requirements·done criteria

→
03PLAN

Product·design·tech

→
04BUILD

Build small

→
05VERIFY

Review·debug·QA

→
06SHIP

Docs·release·retro

01Problem discovery

DISCOVER · no edits

Check why it's needed before what to build

Find the target users, how they solve it now, the most urgent problem and unverified assumptions. AI's suggestions are candidates; a person decides the final product direction.

Codex
Use the gstack-office-hours skill to summarize Focus List's
target users, current alternatives, core problem and minimum feature to test.
Don't change any files yet.
Claude Code
/office-hours

Summarize Focus List's user problem and minimum feature to test.
Don't change any files yet.
Output1-sentence problem · 1 user · 3 assumptionsPass conditionYou can explain it as a user pain, not a feature.
EXAMPLE OUTPUT 01Sample office-hours result

Target user A student managing classes and assignments at the same time

Core problem Even after writing down tasks, it's hard to quickly see the one thing to do now.

Minimum feature to test Add a task and change its done status within 3 seconds.

Assumption to test Users want fast input more than categories.

Human check → Did it reveal a real pain and an assumption to test, not just a feature name like "a to-do app for students"?

02Write the spec

SPEC · no edits

Turn the idea into testable requirements

Fix the scope, user scenarios, normal·exception flows and acceptance criteria. Write observable done criteria instead of "it works well."

Codex
Use the gstack-spec skill to write normal/exception scenarios and acceptance criteria
for empty input, duplicate items and long titles.
Don't build anything yet.
Claude Code
/spec

Write scenarios and acceptance criteria for the three features.
Don't build anything yet.
OutputFeature scope · Out of scope · Acceptance criteriaPass conditionA third person judges success/failure by the same standard.
EXAMPLE OUTPUT 02Sample spec result

Given the input box contains only spaces

When the "Add" button is pressed

Then the item count doesn't increase and "Please enter something" is shown.

Out of scope Login, server storage and categories aren't covered in this lab.

Human check → Can you tell success from failure on screen, without vague phrases like "handles it properly"?

03Plan review

PLAN · no edits

Lock the product, design and tech views in turn

Review separately what to leave out, how it looks to users, and how code and data flow. To move fast, run all three views in a row with autoplan.

Product scopegstack-plan-ceo-reviewClaude: /plan-ceo-review
User experiencegstack-plan-design-reviewClaude: /plan-design-review
Tech structuregstack-plan-eng-reviewClaude: /plan-eng-review
All at oncegstack-autoplanClaude: /autoplan
Use the gstack-plan-eng-review skill to review the current spec.
Include files to change, data flow, failure paths, tests and build order,
and don't build anything yet.
OutputProduct decisions · Screen states · Tech planPass conditionFiles·failure paths·tests are specific and the scope is realistic.
EXAMPLE OUTPUT 03Sample plan review result

Files to change app.js input validation·duplicate check, styles.css error·long title states

Data flow Input → trim → empty check → duplicate check → add to array → re-render

Failure paths Spaces, duplicates differing only by case, titles of 100+ characters, fast repeated clicks

Build order Input validation → duplicate rule → screen states → regression tests

Human check → Open the project yourself to confirm the files and functions AI suggested really exist.

04Build

BUILD · edits allowed from here

Split the plan into small changes and build

Build with the agent's basic features. Ask for one feature at a time, and check the run result and Git diff after each change. gstack strengthens the planning·verification roles before and after building.

Build request
Based on the approved spec and tech plan,
first build only empty-input prevention.
Run the checks and don't touch other features.
Git checkpoint
git status
git diff
git add .
git commit -m "feat: prevent blank tasks"
OutputSmall diff · Run result · Commit per featurePass conditionNo changes outside the spec, and a person reproduced the feature in the app.
EXAMPLE OUTPUT 04Sample Git·browser check after building
$ git diff --stat
app.js | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)

$ git status --short
M app.js

Browser check
✓ Spaces only: stays at 0 items, notice shown
✓ Normal input: 1 item added
✓ Existing done button: works

Human check → Were no unplanned files changed, and does the normal flow still work?

05Review·debug

REVIEW & DEBUG

Find change risks and fix causes, not symptoms

review finds bugs·gaps·structural risks in the diff, and investigate narrows down causes in the order reproduce → evidence → hypothesis → fix. When you only want a report, say "Don't fix anything."

Review
Use the gstack-review skill to review the current diff.
Report only severity, file evidence and how to reproduce; don't fix anything.

Claude: /review
Root cause investigation
Use the gstack-investigate skill to find the cause of duplicate items.
Show the reproduction and evidence first, and don't fix anything before approval.

Claude: /investigate
OutputReview by severity · Reproduction steps · Root causePass conditionEvery point has file/behavior evidence, and guesses are separated from facts.
EXAMPLE OUTPUT 05Sample review·investigate result
P1 · User input can run as HTML

app.js inserts the title with innerHTML. It can be reproduced with malicious HTML input; a text node or textContent is needed.

Root cause

The duplicate check runs after rendering, so a fast second click reads the same array state. The cause is the check order, not button disabling.

Human check → Are severity, file location, reproduction conditions and user impact tied to one piece of evidence?

06QA

QA · User behavior checks

Separate report-only QA from QA with fixes

qa-only actually uses the app and makes only a reproducible report, while qa fixes approved problems and checks again. Do the first run as report-only.

Report only
Use the gstack-qa-only skill to test normal/empty/duplicate/long input,
repeated clicks, refresh and mobile.
Don't fix anything; write expected/actual results.

Claude: /qa-only
Fix after approval
Use the gstack-qa skill to fix only the approved defects
and re-check with the same user flow.

Claude: /qa
OutputQA report · Screenshots · Before/after resultsPass conditionEvery key acceptance criterion has reproducible evidence.
EXAMPLE OUTPUT 06Sample qa-only report
testExpectedActualVerdict
Spaces onlyNot addedEmpty item addedFAIL
Duplicate inputNotice, then block2 addedFAIL
Long title·mobileKeeps line breaksButton pushedFAIL
Normal input1 item added1 item addedPASS

Sample reproduction → 375px screen → enter 120 characters → add → check whether the done button is pushed off screen.

07Release prep

HARDEN & DOCUMENT

Check that security·performance·docs match the build

If there's user input or auth, use cso; if web performance matters, use benchmark; when changes are done, sync docs with document-release.

Securitygstack-csoClaude: /cso
Performancegstack-benchmarkClaude: /benchmark
Docsgstack-document-releaseClaude: /document-release
OutputSecurity/performance results · Latest README · Change notesPass conditionNo serious unresolved risks or doc mismatches.
EXAMPLE OUTPUT 07Sample release prep result

Security 1 P1 user input rendering issue → fixed with textContent and re-checked

Performance Rendering 100 items 18ms → 20ms, under the 50ms limit: PASS

Docs Added how to run, the duplicate rule and the limit that data disappears after refresh to the README

Decision No serious unresolved risks → release candidate

Human check → Did you avoid concluding "safe·fast" without measurements or file evidence?

08Release·retro

SHIP & LEARN

Deliver only verified changes and leave lessons for the next project

ship bundles tests·review·changelog·PR prep. Use land-and-deploy only when a real deploy environment is ready, and finish with a retrospective.

PR prepgstack-shipClaude: /ship
Deploy checkgstack-land-and-deployClaude: /land-and-deploy
Retrogstack-retro · gstack-learnClaude: /retro · /learn
OutputPR checklist · Deploy check · RetroPass conditionOthers understand what changed, why, and how it was verified.
EXAMPLE OUTPUT 08Sample ship·retro result

Change summary Blocked empty input·duplicates and improved the mobile layout for long titles.

Verification 4 acceptance criteria and 8 QA scenarios PASS. Security P1 re-checked.

Remaining limits Data lives only in browser memory, so it disappears after refresh.

Retro If we'd fixed the definition of a duplicate before building, we'd have saved 1 round of rework.

Human check → Can the next person understand the reason for changes, verification evidence and remaining risks without asking?

HUMAN CHECKPOINTS

Four points where AI stops and a person decides

① Approve the problemWhose problem is it② Approve the scopeWhat to leave out③ Approve defectsWhat to fix④ Approve releaseWhether to accept remaining risks

07 / EXTENSION DOWNLOADS

The full course is also
practiced with step-by-step ZIPs.

Each ZIP has the same Focus List project, a step README and a worksheet to fill in. Carry each step's results into the next step's worksheet.

07

Build and Git checkpoints

Small builds · diff · commit per feature

Download ZIP ↓
09

Security·performance·docs

cso · benchmark · document-release

Download ZIP ↓

08 / COMPLETION

Done doesn't mean
"I ran it."

Grading centers on whether each result has evidence and whether a person made the important decisions.

20

Environment setup

Checked the tools and gstack status.

20

Skill choice

Chose the role that fits the goal.

20

Evidence check

Verified AI output with files and behavior.

20

Quality report

Left reproducible review·QA results.

20

Human judgment

Separated assumptions from final decisions.

NEXT PBL PROJECT

Now it's time to apply
one loop to a real project.

Problem definition → Tech plan → Build → Review → QA → Retro