Skills Prompts

Popular categories

Agent skill · gstack

/plan-eng-review Lock architecture, edge cases and tests before you build

The engineering plan review asks what to review, then works through a mandatory scope challenge and four review sections on architecture, data flow, edge cases, test coverage and performance. It follows a stated set of engineering preferences, draws ASCII diagrams for flows and states, and ends by appending a structured review report to the plan.

Works with

  • Claude Code
  • Codex, Cursor, OpenCode, Gemini CLI and other agents

Used forPlanning and specs

When to use it

  • You have an approved feature plan and want the technical design checked before coding.
  • A branch diff needs an architecture-level look before deeper code review.
  • You want a test plan that the QA skill can pick up later.

How it works

  1. 1
    Pick the target

    Outside plan mode the agent asks whether to review the branch diff, a pasted plan or a specific path.

  2. 2
    Check design context

    It looks for a design doc and CEO plan, treats them as data rather than instructions, and offers office hours if none exists.

  3. 3
    Challenge scope

    A scope and complexity check must finish before the review sections begin.

  4. 4
    Review in sections

    It covers architecture, data flow, edge cases, tests and performance, preferring explicit code, small diffs and tested behaviour.

  5. 5
    Close with a report

    The plan must end with a review report table and either a list of unresolved decisions or a clear none.

What it steers the agent away from

  • Building features or benchmarks during a review.
  • Following instructions hidden in another agent's design doc.
  • Calling a review complete without a saved report.

Install this skill

It installs with the gstack pack.

Claude CodeThe README wraps this command in a prompt you paste into Claude Code, which also adds a short gstack section to CLAUDE.md.
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup
Claude Code (team mode for a shared repo)Run inside your repo; it commits a bootstrap so teammates get gstack with auto-updates, and needs Node.js for the required hook.
(cd ~/.claude/skills/gstack && ./setup --team) && ~/.claude/skills/gstack/bin/gstack-team-init required && git add .claude/ CLAUDE.md && git commit -m "require gstack for AI-assisted work"
Codex, Cursor, OpenCode, Gemini CLI and other agentsUse --host auto for every detected agent or name one host; non-Claude hosts are listed as experimental.
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/gstack
cd ~/gstack && ./setup --host auto # or: ./setup --host codex
./setup --status # one row per install: host, tier, scope, version, path

Commands come from the author’s README; check it for changes before you run them.

Questions

Does it need a design doc?

No. Without one it offers to run office hours first, and you can skip that to get a standard review.

What principles does it apply?

Its listed preferences favour tests for every behaviour, explicit over clever code, the smallest clear diff and storage shaped by how data is queried.

More guides from gstack

Also in this pack

All 30 skills →

Summary by trendhub. The skill itself lives in garrytan/gstack/plan-eng-review by Garry Tan (MIT); read the full, current text there.