plan-eng-review

Reviews implementation plans for architecture, code quality, tests, and performance interactively.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill plan-eng-review-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/westkite1201/garden-engine --skill plan-eng-review-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often contain hidden architecture flaws, missing test coverage, and scope creep that only surface after implementation begins. This Skill performs an engineering-manager-style review of your plan before any code is written, catching design issues early when they are cheapest to fix. ## Core Features & Use Cases - Scope Challenge (Step 0): Questions whether existing code already solves sub-problems, flags plans touching 8+ files or 2+ new services, and verifies the plan uses built-in framework capabilities rather than custom solutions. - Section-by-Section Interactive Review: Walks through Architecture, Code Quality, Tests, and Performance one issue at a time via structured questions, always with an opinionated recommendation and completeness scoring. - Test Coverage Enforcement: Detects the project's test framework automatically and pushes for 100% coverage of every codepath in the plan. - Use Case: You have a design doc for a new caching layer and are about to start coding. Run this review to validate the data flow, catch a missing failure scenario for cache invalidation, and confirm the test plan covers edge cases before writing a single line. ## Quick Start Ask the AI to run an engineering review of the current plan to validate the architecture, test coverage, and edge cases before implementation begins.

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 walks through architecture, code quality, tests, and performance section by section. Each issue is presented individually with an opinionated recommendation and tradeoff analysis so you can accept or reject changes before implementation.

What does an engineering manager look for in a design review?

Key checks include blast radius of decisions, whether boring proven technology is used, reversibility of changes, failure scenario coverage, and essential versus accidental complexity. The review also challenges scope, flagging plans that touch more than 8 files or add more than 2 new services.

Does the plan review require a design doc?

A design doc is not strictly required but strongly recommended. If none is found for the current branch, the skill offers to run a prerequisite office-hours step to produce a structured problem statement, then proceeds with a standard review if skipped.

How does the review check test coverage?

It auto-detects the project's test framework from config files like jest.config, pytest.ini, or .rspec, then evaluates every codepath in the plan for corresponding tests. Missing tests are added to the plan so implementation starts with full coverage.

When should I run a plan review versus going straight to code?

Run it whenever you have a plan or design doc and are about to start implementation, especially for changes touching multiple files or introducing new infrastructure. Catching architecture issues at the plan stage is far cheaper than refactoring after code exists.