Gstack Plan
Use before building a feature: challenge the scope, then review architecture, code quality, tests and performance, and end with a plan to build. (gstack)
Install
npx skills add garrytan/gstack --skill gstack-plangit clone --depth 1 https://github.com/garrytan/gstack.git /tmp/gstack
mkdir -p ~/.claude/skills
cp -r /tmp/gstack/qm/sandbox/skills/gstack-plan ~/.claude/skills/gstack-planPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Plan a feature: scope first, then the engineering review Review a plan, not code: do not build the feature. If the user has not given you the plan or feature description, ask for it and stop. **Start here.** In the repository (`cd` into it first: the shell starts in the workspace root), run with `execute` to see what already exists: ```sh git log --oneline -10 ls ``` Then read the files the plan touches. Work through Scope Challenge, then Sections 1-4 in order; for each finding give severity, a recommendation and the alternative. Ask about decisions that change scope in one message and stop until the user answers. Finish with the revised plan: what to build, in order, the files it touches, the tests that prove it, and what is NOT in scope. ## My engineering preferences (use these to guide your recommendations): * **Shared code:** require common behavior and improved reliability or net savings; similar-looking code alone is insufficient. * **Tests:** every behavior tested; no test without a regression it would catch. * **Enough engineering:** avoid fragility and premature abstraction/complexity. * **Edge cases:** thorough handling over speed. * **Explicit over clever.** * **Right-sized diff:** smallest clear change; rewrite a broken foundation when necessary.
Details
- Skill name
gstack-plan- Repository
- garrytan/gstack
- Path
qm/sandbox/skills/gstack-plan/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Gstack Plan skill do?
Use before building a feature: challenge the scope, then review architecture, code quality, tests and performance, and end with a plan to build. (gstack)
How do I install the Gstack Plan skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add garrytan/gstack --skill gstack-plan. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Gstack Plan popular?
It lives in garrytan/gstack, which has 141,991 GitHub stars and 20,959 forks, and is included in 2 curated skill lists.
Related skills
Autoplan
142kgarrytan/gstack
Auto-review pipeline — runs the CEO, design, eng and DX reviews in order (lean run: one reviewer), auto-deciding. Use for: run all reviews, automatic review pipeline. (gstack)
Benchmark
142kgarrytan/gstack
Web performance regression detection. Use for: web performance benchmark, check page speed. (gstack)
Benchmark Models
142kgarrytan/gstack
Cross-model benchmark for gstack skills. Use for: cross model benchmark, compare claude gpt gemini. (gstack)
Plan Devex Review
142kgarrytan/gstack
Interactive developer experience plan review. Use for: developer experience review, dx plan review. (gstack)
Gstack Openclaw Office Hours
142kgarrytan/gstack
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
Plan Eng Review
142kgarrytan/gstack
Use when you plan a feature before building it, or review a plan: locks in architecture, data flow, diagrams, edge cases, test coverage and performance. Use for: plan a feature, review architecture, eng plan review. (gstack)
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.