Don't build right away
Check the user's problem and scope, and surface assumptions before building.
3 HOURS HANDS-ON LECTURE
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.
gstack workflow
Think → Plangstack isn't a coding model; it's a development workflow that gives AI roles, order and quality standards.
01 / ORIENTATION
Check the user's problem and scope, and surface assumptions before building.
Run product, tech, review and QA views as separate skills.
AI output isn't the answer. Check it with files, Git diff and real behavior.
02 / 180-MINUTE ROADMAP
Understand gstack and the differences between the two run environments.
Check Git, Bun, accounts and your terminal setup.
Install each tool and do a first read task in the project.
Register the skills in your chosen host and check the status.
Learners with install problems catch up during this time.
Run office-hours and plan-eng-review.
Experience the difference between a code view and a user behavior view.
Compare the two tools' results and write a plan to apply them to your PBL.
03 / SETUP
Learners pick one track and follow along. The instructor demos both environments side by side.
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
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.
A window where you give the computer commands as text.
The terminal built into Windows.
Copy it, paste it into PowerShell and press Enter.
An optional feature that runs Ubuntu Linux inside Windows.
Install right from PowerShell without learning another operating system.
Use this when you need a uniform Linux dev environment or the native install is blocked.
Press the Windows key, search for PowerShell and run it. If you see PS C:\Users\username> in the window, you're good.
Paste the commands below one line at a time and press Enter.
winget install --id Git.Git -e
winget install OpenJS.NodeJS.LTSExpected result · After the install-complete message, close and reopen PowerShell.
powershell -c "irm bun.sh/install.ps1|iex"Open a new PowerShell and type bun --version; if a number appears, it worked.
powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"codex --version
codexOn first run, follow the on-screen steps to log in with one of the offered options, like a ChatGPT account.
winget install Anthropic.ClaudeCodeclaude --version
claude doctor
claudeYou need an account that can use Claude Code. If you only use one tool, you can skip this step.
git --version
node --version
npm --version
bun --version
codex --version
claude --versionIf each line shows a version number, go to the next step.
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git "$HOME\gstack"
cd "$HOME\gstack".\setup.ps1 --host codex
.\setup.ps1 --host claude
.\setup.ps1 --statusIf you only use one tool, run only that host's command. If codex or claude appears in the status table, it worked.
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# If you chose Codex
codex
# If you chose Claude Code
claudeAlways check git status and git diff before and after AI work.
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.
wsl --installWhen the install finishes, restart your computer.
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.
sudo apt update
sudo apt install -y git curl unzip
curl -fsSL https://bun.com/install | bash
source ~/.bashrccurl -fsSL https://chatgpt.com/codex/install.sh | sh
curl -fsSL https://claude.ai/install.sh | bashgit clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/gstack
cd ~/gstack
./setup --host codex
./setup --host claude
./setup --statusIf you install only Codex on Windows and gstack in WSL, they use different home folders. Install everything on Windows or everything in WSL2 Ubuntu.
Close PowerShell completely, open a new one and try again.
Run it like powershell -ExecutionPolicy Bypass -File .\setup.ps1 --host codex.
Set git config user.name "student" and a local email.
Quit Codex·Claude, open a new session and check .\setup.ps1 --status.
Open a new PowerShell and check bun --version again.
Don't turn off security settings; tell the instructor and switch to the WSL2 track.
Read and edit the project in the terminal, and name gstack skills in plain language.
curl -fsSL https://chatgpt.com/codex/install.sh | shnpm install -g @openai/codexcodex --version
codexgstack's officially supported environment; call the main skills with slash commands.
brew install --cask claude-codenpm install -g @anthropic-ai/claude-codeclaude --version
claude doctor
claudeCOMMON STEP
Get the gstack source from the official Git repository and register it in your chosen AI tool's skills folder.
git clone --single-branch --depth 1 \
https://github.com/garrytan/gstack.git ~/gstack
cd ~/gstack# Codex
./setup --host codex
# Claude Code
./setup --host claude./setup --statusMETHOD B · PROMPT-DRIVEN SETUP
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.
Codex can't install itself. Finish installing and logging in to Codex CLI with the official install command above before starting this.
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
codexFirst, read-only, check the OS, shell, required tools and any existing install.
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.Check that the OS and install path Codex shows match your real environment. Don't put passwords, API keys or auth codes in prompts.
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
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.
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.If you see a command you don't know, don't approve it; ask "Explain what this command changes."
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"
codexFirst 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
We don't use a GitHub lab repository. Download the ZIP, extract it and create a local Git repository.
Download lab files
Extract and move in
Create a local baseline
Run Codex or Claude
cd downloaded-lab-folder/project
git init
git add .
git commit -m "Lab start state"
git status15 MIN · Setup
Scripts to check Git, Bun, Codex and Claude versions, plus a learner checklist.
20 MIN · First run
Run office-hours on the Focus List app, which has built-in problems on purpose.
25 MIN · Plan
Review components, data flow, exceptions and tests with plan-eng-review.
20 MIN · Verify
See the difference between review and qa-only views and write a reproducible report.
INSTRUCTOR & OFFLINE PACK
The 10-step materials, sample app and worksheets in one ZIP.
05 / PROMPT LAB
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.
/office-hours
Summarize this project's target users, the problem it solves,
core value, smallest core feature and unverified assumptions.
Don't change the code yet.
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
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.
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.
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.
Problem·users
Requirements·done criteria
Product·design·tech
Build small
Review·debug·QA
Docs·release·retro
DISCOVER · no edits
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.
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./office-hours
Summarize Focus List's user problem and minimum feature to test.
Don't change any files yet.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"?
SPEC · no edits
Fix the scope, user scenarios, normal·exception flows and acceptance criteria. Write observable done criteria instead of "it works well."
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./spec
Write scenarios and acceptance criteria for the three features.
Don't build anything yet.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"?
PLAN · no edits
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.
gstack-plan-ceo-reviewClaude: /plan-ceo-reviewgstack-plan-design-reviewClaude: /plan-design-reviewgstack-plan-eng-reviewClaude: /plan-eng-reviewgstack-autoplanClaude: /autoplanUse 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.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.
BUILD · edits allowed from here
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.
Based on the approved spec and tech plan,
first build only empty-input prevention.
Run the checks and don't touch other features.git status
git diff
git add .
git commit -m "feat: prevent blank tasks"$ 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: worksHuman check → Were no unplanned files changed, and does the normal flow still work?
REVIEW & DEBUG
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."
Use the gstack-review skill to review the current diff.
Report only severity, file evidence and how to reproduce; don't fix anything.
Claude: /reviewUse 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: /investigateapp.js inserts the title with innerHTML. It can be reproduced with malicious HTML input; a text node or textContent is needed.
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?
QA · User behavior checks
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.
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-onlyUse the gstack-qa skill to fix only the approved defects
and re-check with the same user flow.
Claude: /qaSample reproduction → 375px screen → enter 120 characters → add → check whether the done button is pushed off screen.
HARDEN & DOCUMENT
If there's user input or auth, use cso; if web performance matters, use benchmark; when changes are done, sync docs with document-release.
gstack-csoClaude: /csogstack-benchmarkClaude: /benchmarkgstack-document-releaseClaude: /document-releaseSecurity 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?
SHIP & LEARN
ship bundles tests·review·changelog·PR prep. Use land-and-deploy only when a real deploy environment is ready, and finish with a retrospective.
gstack-shipClaude: /shipgstack-land-and-deployClaude: /land-and-deploygstack-retro · gstack-learnClaude: /retro · /learnChange 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
07 / EXTENSION DOWNLOADS
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.
office-hours · spec
Download ZIP ↓plan-ceo · plan-design · plan-eng
Download ZIP ↓Small builds · diff · commit per feature
Download ZIP ↓review · investigate · qa-only · qa
Download ZIP ↓cso · benchmark · document-release
Download ZIP ↓ship · land-and-deploy · retro · learn
Download ZIP ↓08 / COMPLETION
Grading centers on whether each result has evidence and whether a person made the important decisions.
Checked the tools and gstack status.
Chose the role that fits the goal.
Verified AI output with files and behavior.
Left reproducible review·QA results.
Separated assumptions from final decisions.
NEXT PBL PROJECT
Problem definition → Tech plan → Build → Review → QA → Retro