plan-eng-review

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

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fullya99/simple-blog-page --skill plan-eng-review-fullya99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/fullya99/simple-blog-page/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/fullya99/simple-blog-page --skill plan-eng-review-fullya99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often hide scope creep, missing test coverage, and unexamined architectural tradeoffs until code review or production. This Skill forces a structured, engineering-manager-style review of any implementation plan before code is written, surfacing issues one at a time with opinionated recommendations. ## Core Features & Use Cases - Scope Challenge (Step 0): Identifies existing code that already solves sub-problems, flags overbuilt plans, and offers scope reduction, big-change, or small-change review modes. - Four-Section Interactive Review: Walks through architecture, code quality, test coverage, and performance, presenting each issue individually with lettered options and a stated recommendation. - Mandatory Outputs: Produces a test coverage diagram, failure-mode analysis, "NOT in scope" list, "What already exists" audit, and structured TODOS.md proposals. - Use Case: Before implementing a multi-service feature, run this review to catch an N+1 query risk, a missing edge-case test, and an unnecessary new abstraction — each resolved interactively before any code changes. ## Quick Start Ask the assistant to review your implementation plan using the plan-eng-review skill before making any code changes.

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 writing code?▼

Run this Skill on your plan and it performs a structured review across architecture, code quality, tests, and performance. Each issue is presented individually with lettered options and an opinionated recommendation, so decisions are made before implementation starts.

What does an engineering plan review cover?▼

The review covers four sections: architecture (component boundaries, data flow, security), code quality (DRY violations, error handling, over-engineering), tests (coverage diagram for new codepaths), and performance (N+1 queries, caching, memory). It also produces scope and failure-mode analyses.

Can I use this for small changes instead of large plans?▼

Yes, the Skill offers a SMALL CHANGE mode that compresses the review into one combined pass, picking the single most important issue per section. It still requires the scope challenge step and a test diagram, but batches questions into one round.

Does the plan review check test coverage?▼

Yes, the test review builds a diagram of all new UX, data flows, codepaths, and branching logic, then verifies each item has a corresponding test. Failure modes without tests and error handling are flagged as critical gaps.

What happens to deferred work found during plan review?▼

Deferred work is captured in a "NOT in scope" section with rationale, and each potential TODO is proposed individually with what, why, pros, cons, context, and dependencies. You choose per item whether to add it to TODOS.md, skip it, or build it now.