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)

141,991 stars 20,959 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add garrytan/gstack --skill gstack-plan
Manual install
git 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-plan

Personal 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.
Read the full skill on GitHub

Details

Skill name
gstack-plan
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

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.