Environment Setup & How to Use It
One foundation layer + one framework + two small files — and you're done. If things go smoothly, it takes 30 minutes.
Three layers — that's all you need to install
Don't let "installation" scare you. The whole system is three layers — once you understand them, you're calm.
Standalone skills
Single files — just copy them in: competitor-watch (competitive research) · prd-generator (write PRDs)
gstack framework
Install once and get 70+ skills: office-hours / design-shotgun / design-html / qa / make-pdf …
Claude Code itself
The foundation app — without this, nothing works.
Essential skills checklist
Core 7 (must install — mapped to the five stages)
| Skill | Purpose | Source | Stage |
|---|---|---|---|
/competitor-watch | Competitive analysis | Standalone skill | Discover |
/office-hours | Sharpen ideas, clarify requirements | gstack | Define |
/prd-generator | Generate PRD | Standalone skill | Define |
/design-shotgun | Generate multiple design options at once | gstack | Design |
/design-html | Turn design into runnable prototype | gstack | Develop |
/qa | Automated testing to find bugs | gstack | Validate |
/make-pdf | Convert markdown to polished PDF | gstack | All stages |
Advanced 6 (use once you're comfortable — all from gstack)
| Skill | Purpose |
|---|---|
/design-consultation | Define a complete design system (colors / typography / style) |
/plan-ceo-review | Challenge your plan from a "CEO lens" |
/plan-eng-review | Review your plan from a "tech lens" |
/investigate | Systematically diagnose root causes of problems |
/context-save · /context-restore | Save / restore working state across sessions |
/learn | Capture and retrieve team knowledge |
Installation steps
Option A (recommended): team lead shares a working config
Easiest option, least error-prone. The lead packages up their entire .claude\skills\ directory and sends it out.
Each member:
| 1 | Install Claude Code itself (see Option B, step ①) |
| 2 | Unzip the received skills package into C:\Users\<you>\.claude\skills\ |
| 3 | Go into the gstack directory and run ./setup |
| 4 | Run the verification checks (next section) |
Option B: install from scratch individually
① Install Claude Code
npm install -g @anthropic-ai/claude-code
After installation, sign in (team uses a shared Pro/Team subscription). If you don't have Node/npm, install Node.js first.
② Install gstack framework (one line: clone + auto-initialize)
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack \ && cd ~/.claude/skills/gstack && ./setup
gstack self-updates. To upgrade manually, just say /gstack-upgrade in any conversation.
③ Add standalone skills
Copy the competitor-watch and prd-generator directories into ~/.claude/skills/.
/browse throw errors, go into the gstack directory and run bun install && bun run build to install dependencies.Verify: how to confirm it's all working
Don't jump straight into work after installing — spend 2 minutes on a smoke test first.
Confirm the core runs
Type claude in the terminal. If a conversation interface opens = Layer 1 OK.
claude
Confirm all skills are present
Type / in the conversation. If you see a long list of skills = framework and skills OK.
/ (confirm the core 7 are all there)
Run a real skill
If it starts asking you questions = everything is ready, time to work.
/office-hours I want to build a team weekly report aggregator tool
How to use it end-to-end
Chain all the skills into a complete workflow. Know this line and you always know which skill to reach for.
watch
/prd-generator
shotgun
/design-html
Standard moves (follow this playbook)
| Step | What to do |
|---|---|
| 0 Create project | Create a folder at D:\PM\<project-name>\, go in, say "help me initialize this project" |
| 1 Discover | /competitor-watch analyze [competitor URL], focus on [area of interest] |
| 2 Define | /office-hours I want to build [idea] → /prd-generator write a complete PRD |
| 3 Design | /design-shotgun make 3 style options for [some page] |
| 4 Develop prototype | /design-html to build, then add one feature at a time through conversation (small steps, fast cycles) |
| 5 Validate | /qa test this prototype and list all the issues |
/ to pick the right skill for each. To deliver a document, use /make-pdf.Ongoing maintenance & onboarding new members
Ongoing maintenance (team lead to watch)
| Task | How to do it |
|---|---|
| Upgrade framework | Say /gstack-upgrade in a conversation, or enable auto-update |
| Add new skills | Put the skill directory in ~/.claude/skills/ and restart Claude Code |
| Enforce standards | Share base constraints in each project's CLAUDE.md |
| Capture knowledge | Add good tips and hard-learned lessons to the PM Standard Work Guide |
Fastest onboarding path for new members
- Set up environment (Option A — ask lead for the package)
- Run through the smoke tests
- Take one small requirement through all five stages
- Once that's done — you're good to go
