plan-eng-review

Review engineering plans for architecture, data flows, edge cases, and test coverage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams conduct thorough, opinionated plan reviews to catch architecture issues, data-flow gaps, edge cases, missing test coverage, and performance risks before coding starts.

Core Features & Use Cases

  • Interactive architecture and plan review with structured recommendations and trade-offs.
  • Verification of data flows, diagrams, edge cases, test coverage, and performance implications.
  • Alignment guidance for stakeholders and governance on design decisions.
  • Proactive improvement suggestions when design quality could be enhanced.

Quick Start

Describe the feature plan in brief and ask the skill to review for completeness and risks.

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 what does it evaluate?

An engineering plan review evaluates architecture designs by surfacing data flows, edge cases, test coverage, and performance implications. It prompts for structured trade-offs and recommended actions to catch system design risks before coding starts.

How do I review a system architecture design for missing edge cases?

To review a system architecture design for missing edge cases, describe the feature plan briefly and request a completeness check. The review enforces explicit edge-case handling, verifies data flows, and suggests documentation and tests.

Does this engineering design review work for new component architectures?

Yes, this engineering design review works for new component architectures. It applies to plans detailing new architectures, system designs, or design reviews for features, verifying test coverage and performance implications for components.

What is the best way to document trade-offs during a design review?

The best way to document trade-offs during a design review is to enforce structured analysis. This approach surfaces architecture issues and data-flow gaps, prompting stakeholders for explicit trade-offs and recommended actions to align governance.

When do I need to perform a risk assessment on a technical plan?

You need to perform a risk assessment on a technical plan when new architectures or system designs are proposed. It catches performance risks, verifies test coverage, and enforces safe analysis with explicit edge-case handling before development begins.