plan-eng-review

Name: plan-eng-review
Availability: InStock
Author: GenEd

Evaluates engineering plans and architecture decisions for completeness, risk, and feasibility.

Updated Mar 30, 2026

Search Tags:#performance #data flow #edge cases #test coverage #architecture review #plan review #engineering review

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill plan-eng-review-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/plan-eng-review
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill plan-eng-review-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch architecture mistakes before implementation starts, when fixes are cheap and the blast radius is still small. It is built for engineering plans that need a hard review on data flow, test strategy, edge cases, performance, and operational risk.

Core Features & Use Cases

Architecture review: Check whether the proposed system design is boring, reversible, and actually shippable.
Edge case and failure analysis: Pressure-test what happens when inputs are weird, dependencies fail, or users hit the unhappy path.
Test and performance review: Push for coverage that matches the risk, and call out slow paths, hidden coupling, and missing validation.
Use case: You have a design doc for a new feature and want an opinionated pass that finds the landmines before anyone writes code.

Quick Start

Ask the plan-eng-review skill to review your architecture, data flow, edge cases, tests, and performance before you start coding.

Frequently Asked Questions about plan-eng-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is an engineering plan review and when do I need one before coding?▼

An engineering plan review evaluates architecture decisions, data flow, and edge cases before implementation starts. You need one when you have a design doc and want to catch system design mistakes while fixes are cheap and the blast radius is small.

How do I review edge cases and failure modes in a system design doc?▼

To review edge cases in a system design doc, pressure-test what happens when inputs are weird, dependencies fail, or users hit the unhappy path. This failure analysis spots operational risks and hidden coupling before code is written.

Does an architecture review help with test coverage planning?▼

Yes, an architecture review helps with test coverage planning by pushing for coverage that matches the actual operational risk. It evaluates whether your test strategy adequately addresses slow paths, failure modes, and edge cases.

How do I evaluate performance tradeoffs in an engineering plan?▼

To evaluate performance tradeoffs in an engineering plan, review the proposed data flow mapping to call out slow paths and hidden coupling. This ensures the system design is actually shippable and performance bottlenecks are identified early.

What are the limitations of relying on a design doc review for operational risk?▼

A design doc review focuses on theoretical completeness and reversibility but cannot guarantee production stability. Its limitation is that it relies on interactive issue spotting and opinionated recommendations before real-world runtime behavior is observed.