plan-eng-review

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

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill plan-eng-review-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/gstack-plan-eng-review
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill plan-eng-review-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often contain hidden architecture flaws, missing edge cases, scope creep, and inadequate test coverage that only surface during implementation. This Skill performs an engineering-manager-style review of a plan or design doc before any code is written, catching issues early when they are cheapest to fix. ## 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 minimal-change approaches with web-searched best practices. - Interactive Section Reviews: Walks through Architecture, Code Quality, Tests, and Performance one issue at a time via structured questions, each with an opinionated recommendation and completeness scoring. - Test Coverage Mapping: Traces every codepath in the plan, draws ASCII diagrams of branches and error paths, and ensures the plan includes tests for 100% coverage before implementation starts. - Use Case: Before implementing a new feature, run this review on your design doc to catch a missing error-handling path in the data flow and an over-engineered service boundary, then lock in a revised plan. ## 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 engineering plan before writing code?

Run this Skill on your plan or design doc and it walks through scope, architecture, code quality, tests, and performance section by section. Each issue is presented individually with an opinionated recommendation and options, so you decide the direction before implementation starts.

What does an engineering manager-style plan review cover?

It covers scope challenge (existing code reuse, complexity smells), architecture (coupling, data flow, failure scenarios), code quality (DRY violations, error handling), test coverage (every branch and error path mapped), and performance. It also checks whether built-in framework features could replace custom solutions.

Does the plan review require a design doc to work?

No, but it works better with one. The Skill checks for a design doc for the current branch first; if none exists, it offers the prerequisite /office-hours skill to produce a structured problem statement, or proceeds with a standard review if you skip.

How does the review ensure full test coverage in the plan?

It traces every codepath in the plan from entry points through branches and error paths, draws ASCII diagrams of the execution flow, and maps user interaction edge cases like double-submits and stale sessions. Any branch without a planned test is flagged so the plan includes complete coverage.

When should I not use an interactive plan review?

Skip it for trivial changes like typo fixes or single-line bug fixes where a full architecture walkthrough adds no value. It is designed for plans touching multiple components, new services, or non-obvious data flows where early feedback prevents expensive rework.