plan-eng-review

Reviews implementation plans for architecture, test coverage, edge cases, and scope before coding begins.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill plan-eng-review-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/gstack/plan-eng-review
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill plan-eng-review-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often hide architecture flaws, missing edge cases, and scope creep that only surface after code is written. This Skill runs an engineering-manager-style review of your plan or design doc before implementation, catching issues when they are cheapest to fix. ## Core Features & Use Cases - Scope Challenge (Step 0): Identifies existing code that already solves sub-problems, flags plans touching 8+ files or 2+ new services, and challenges shortcuts against a completeness standard. - Interactive Issue Walkthrough: Presents each finding with concrete tradeoffs, an opinionated recommendation, and completeness scores, then asks for your decision before proceeding. - Architecture & Test Review: Evaluates data flow, ASCII diagrams, edge cases, test coverage, and performance using engineering-leadership heuristics like blast radius, boring-by-default technology choices, and reversibility. - Use Case: You have a design doc for a new billing feature and are about to start coding. Run this review to catch an N+1 query pattern, a missing failure-mode test, and an unnecessary new service before writing a single line. ## Quick Start Ask the AI to run an engineering review of the current plan or design doc on this branch before starting 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 this review on your plan or design doc before writing code. It checks scope against existing code, challenges plans touching more than 8 files or 2 new services, and walks through architecture, edge cases, and test coverage interactively with recommendations.

What does an engineering plan review check for?

It checks whether existing code already solves sub-problems, whether the plan is the minimum viable change, edge case handling, test coverage, performance risks like N+1 queries, and whether custom solutions duplicate framework built-ins.

Do I need a design doc before running a plan review?

No, but it helps. If no design doc is found for your branch, the skill offers to run a structured office-hours session first to produce one. You can skip that and proceed with a standard review of whatever plan exists.

When should I not use an interactive plan review?

Skip it for trivial changes like typo fixes or config tweaks where review overhead exceeds the risk. It is designed for plans with real architectural decisions, new services, data model changes, or multi-file features.

Can the plan review validate architecture choices against current best practices?

Yes. For each architectural pattern or infrastructure component the plan introduces, it can search for framework built-ins, current best practices, and known pitfalls. If web search is unavailable, it falls back to in-distribution knowledge and notes the limitation.