plan-eng-review

Reviews implementation plans for architecture, code quality, tests, and performance before coding begins.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill plan-eng-review-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill plan-eng-review-dhnpmp-tech

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 interactive engineering-manager-style review of a plan or design doc, catching issues before any code is written. ## Core Features & Use Cases - Scope Challenge (Step 0): Identifies existing code that already solves sub-problems, flags complexity smells (8+ files or 2+ new services), and recommends scope reductions before reviewing details. - Section-by-Section Interactive Review: Walks through Architecture, Code Quality, Tests, and Performance one issue at a time via AskUserQuestion, with opinionated recommendations and completeness scores for each option. - Test Coverage Enforcement: Detects the project's test framework automatically and pushes for 100% coverage of every codepath in the plan, including edge cases and error paths. - Use Case: You have a design doc for a new feature and are about to start coding. Run this review to catch a missing failure scenario in your data flow, an over-engineered abstraction, and three untested edge cases — before they become expensive refactors. ## Quick Start Ask the AI to run an engineering review of the current plan or design doc for 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 an engineering plan review that challenges scope first, then walks through architecture, code quality, tests, and performance section by section. Each issue is presented individually with an opinionated recommendation and tradeoffs so you can accept or reject changes interactively.

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

Key checks include blast radius of decisions, whether boring proven technology is used, reversibility of changes, failure scenarios per integration point, and essential versus accidental complexity. The review also flags scope creep when a plan touches more than 8 files or adds more than 2 new services.

Does the plan review require a design doc to work?

No, a design doc is optional. If none is found for the current branch, the skill offers to run a prerequisite office-hours step to produce one, or proceeds with a standard review using the plan as-is.

How is test coverage evaluated during plan review?

The review auto-detects the project's test framework from CLAUDE.md or config files, then checks that every codepath in the plan has corresponding tests. Missing tests are added to the plan so implementation starts with full coverage including edge cases.

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

Run it when you have a plan or design doc and are about to start coding, especially for changes touching multiple files or introducing new architecture. It catches structural issues when they cost minutes to fix instead of hours of refactoring later.