plan-eng-review

Reviews implementation plans for architecture, tests, edge cases, and performance interactively.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill plan-eng-review-vertakhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill plan-eng-review-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often hide architecture flaws, missing test coverage, and scope creep that only surface after coding starts. This Skill performs an engineering-manager-style review of a plan or design doc before implementation, walking through issues interactively with opinionated recommendations. ## Core Features & Use Cases - Scope Challenge (Step 0): Checks whether existing code already solves sub-problems, flags plans touching 8+ files or 2+ new services, and verifies the plan is not a shortcut when completeness is cheap. - Structured Review Sections: Walks through Architecture, Code Quality, Tests, and Performance one section at a time with at most 8 top issues each, using ASCII diagrams for data flow and test coverage. - Opinionated Recommendations: Every issue comes with concrete tradeoffs, a recommendation, completeness scoring, and an AskUserQuestion prompt before any direction is assumed. - Use Case: You have a design doc for a new billing feature and are about to start coding. Run the review to catch an N+1 query risk, a missing failure-path test, and an unnecessary new service before writing a line of code. ## Quick Start Ask the AI to run an engineering review of the current plan or design doc to lock in the architecture before implementation.

Frequently Asked Questions about plan-eng-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an implementation plan before coding?▼

Run an engineering plan review that challenges scope first, then walks through architecture, code quality, tests, and performance section by section. Each issue includes concrete tradeoffs and an opinionated recommendation, and you confirm direction interactively before anything is assumed.

What does an engineering plan review check for?▼

It checks whether existing code already solves sub-problems, flags plans touching more than 8 files or 2 new services, verifies test coverage and edge cases, and assesses performance risks. It also cross-references deferred TODOs and checks distribution pipelines for new artifacts.

When should I run a plan review in my workflow?▼

Run it after you have a plan or design doc but before writing code. It works best with a design doc as input; if none exists, it can offer a prerequisite step to produce a structured problem statement first.

Does the plan review make code changes automatically?▼

No. It only reviews the plan and asks for your input on every issue through interactive prompts. No code changes happen until you accept or reject each recommendation and the plan is locked in.

What are the limitations of an interactive plan review?▼

It depends on the quality of the plan or design doc provided, and vague inputs produce shallower findings. It also defers to your judgment on scope decisions, so it cannot enforce reductions you reject.