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

Source: https://trendhub.net/skills/garrytan-gstack/plan-eng-review
Skill folder: https://github.com/garrytan/gstack/tree/main/plan-eng-review
Pack: gstack (https://trendhub.net/skills/garrytan-gstack)
Works with: Claude Code, Claude Code (team mode for a shared repo), Codex, Cursor, OpenCode, Gemini CLI and other agents

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.

## 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. **Pick the target**: Outside plan mode the agent asks whether to review the branch diff, a pasted plan or a specific path.
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. **Challenge scope**: A scope and complexity check must finish before the review sections begin.
4. **Review in sections**: It covers architecture, data flow, edge cases, tests and performance, preferring explicit code, small diffs and tested behaviour.
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.

## What it can touch

Reads the plan, repo and git state, may run short probes of current behaviour, and writes the review report and log.

## Pairs well with

- `/office-hours`
- `/plan-ceo-review`
- `/qa`

## 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.
